clobbering version of getdown from r274, and that environment clobbering seems to prevent launching
on Linux and some Windows installs. Now if we want to release with the fixed version of environment
setting and an environment.txt, the clobbering version will run as part of the update, process the
newly downloaded environment.txt, and never launch again. By renaming it env.txt, we can skirt
around that whole fiasco and environment setting won't go into effect until the new getdown is
running.
2. getdown uses 30 classes from samskivert.util
3. Macs have case-preserving, case-insensitive filesystems
4. getdown unpacks its proguarded jar to combine it with the retroweaver runtime
With these 4 conditions in place, getdown-retro-pro will bafflingly lack
certain classes. Using the update attribute on ant's jar task allows the
runtime to be inserted without proguarded files touching the filesystem, and I
can start regrowing my hair.
lock="true" param is passed to the applet.
Release the lock when launching the application directly from getdown,
navigating away from the applet and borking. Hopefully one of the first two
releases will allow invoking directly to work in an applet, but applets seem to
share the lock on my Mac, so I haven't been able to test it.
pesky and pushes annoying requirements on users of the Getdown download
services (like Yohoho and ToyBox).
Instead we'll allow Downloader.download() to return false to indicate that the
download was aborted by an observer, and the observers will simply return false
to indicate that they wish the download to be aborted.
While I was in there, I moved the Downloader and its concrete implementations
into a getdown.net package because it annoyed me that they were in
getdown.launcher.
instances of getdown from stepping on each others toes. Getdown now checks the
modtime of getdown.txt when it starts, during its downloading, and before
launching the real app. If at any of these points the modtime has changed from
when it was last checked, getdown assumes that means another instance is
running and bails to let the other instance do its magic.
Mainly this is for a delayed, silent installer that wants to launch after its
delay, but not if getdown has been run manually after it was launched. Also, if
someone manages to get a little click happy on their installer, this will keep
multiple instances from fighting for the bandwidth to download the same file
simultaneously.
Andrzej Kapolka