Small patches

[Anjo Krank]

Hi Milan,

here's two patches, hope you apply them (with "patch -p0
<patchfile.txt").

One to fix the classpath for the sample apps so they don't reference a
milgra.jar that doesn't exist.

[Anjo Krank]

How nice... the google group doesn't handle text attachements...
here's another try with a zip.

Cheers, Anjo

[Milan Toth]

Hello,

thanks for the patches, i'll check them asap.

> Also, as I think I told you before, Eclipse is pretty good at hot-
> swapping, meaning that you can change your app while it runs. This is
> an extreme boost to productivity, as you don't have to go through all
> the stop-build-start-goto stuff you need to do when you don't do it.
> You can even change methods while you have set a breakpoint in them.
> Here's a patch that does this for the unit test example (which doesn't
> work as the streams/phone.flv is missing). After applying, you can
> right-click on MilGraUnitServer/Application.launch and chose "Run as >
> Application" or "Debug as > Application".

Well, i've never tried this, since i'm always suspicious about every
running thing when magic mistakes happening, i never know if they are
because of some IDE malfunction, or my stupidity :, so seeing the
startup script starting up is always a milestone for me. ) but i'll
give it a try, i mustnt be so orthodox.

> Also, I think you should reconsider how apps are started. It is a bit
> unpractical to let them all start in the same package, in particular
> when you have more than one project. I use cmd-shift-t (Open Type) a
> few hundred times a day, and it is a bit of a nuisance to distinguish
> between all those same-named classes. It would be easier if I could
> name them the way I want (I'd do it with a prefix). If you insist on
> your jar-loading, you should at least set the main class in the app
> jar's manifest and read that out. This way, you can use any class
> name, it doesn't even have to be named "Application".
I was thinking about this at the beginning, but its very annoying for
a newbie or for a quick application to deal with the manifest file.
I'll wait until the the common appereance of java 6, where in the jar
archiver you can specify the entry point simply in a parameter.

> And finally the build files seem to be missing, too...
Yeah, it only applies for my folder system, i use a separate
production directory with the testing stuff, but i can upload it to
the root of the server, you are right.

> Cheers, Anjo

Cheers, Milan

[Anjo Krank]

> I was thinking about this at the beginning, but its very annoying for
> a newbie or for a quick application to deal with the manifest file.
> I'll wait until the the common appereance of java 6, where in the jar
> archiver you can specify the entry point simply in a parameter.

Well, you could still leave the old schema in place as a fallback.
I.e: check the manifest, is not set, use application.Application.

Cheers, Anjo

[Milan Toth]

Good idea!!! :D

Milan