AfflictionNetworks/getdown
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
450 Commits 1 Branch 0 Tags
f4ee20651638d1f375a67c3b79c1ad35535c02b8
Commit Graph

450 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Michael Bayne f4ee206516 We need all active code resources here. 2013-01-10 16:38:42 -08:00
Michael Bayne ce171faa47 Add support for code resources in auxgroups. 
Usage is as you might expect:

auxgroups = foo
foo.code = foo-code.jar
foo.resource = foo-wontbeunpacked.jar
foo.uresource = foo-willbeunpacked.jar
 2013-01-09 22:15:16 -08:00
Michael Bayne b2ef1f57ec [maven-release-plugin] prepare for next development iteration 2013-01-09 13:02:15 -08:00
Michael Bayne 40e9ab7a82 [maven-release-plugin] prepare release getdown-1.3 2013-01-09 13:02:12 -08:00
Michael Bayne 4a7d8d3b05 Update our SCM to Git since that's what we use now. 2013-01-09 13:01:25 -08:00
Michael Bayne 8f3c990d6e We need to keep some classfile attributes. 
Otherwise compiling against the resulting jar can be hosed.
 2013-01-09 12:57:36 -08:00
Jamie Doornbos bfb23911f0 Added support for username:password@ prefix on URLs. 2012-12-19 11:11:48 -08:00
Mark Johnson f9d056ba8a Preparing for 1.3-SNAPSHOT development. 2012-12-10 16:21:27 -08:00
Mark Johnson bb6e44c927 Preparing for getdown-1.2.5 release. 2012-12-10 16:12:25 -08:00
Mark Johnson 557dcca4ac The check_unpacked setting will now to version checks so that unpacking can occur if an update is 
done by an external source outside of getdown.
 2012-12-10 13:05:22 -08:00
Mark Johnson 6b85340ed4 You can now override the scheme and domain of the appbase and latest URLs specified in your 
getdown.txt by setting the appbase_domain system property when launching getdown as an application
 2012-12-07 18:20:25 -08:00
Michael Bayne bfb4b06b30 Bump Proguard to 4.8 to make things work with Java 7. 2012-12-04 16:23:03 -08:00
Michael Bayne bb61a43a71 OpenJDK omits plugin.jar. Obtain it from icedtea-web if available. 2012-07-02 17:44:16 +00:00
Mark Johnson bbb8e74bab Preparing for 1.3-SNAPSHOT development. 2012-06-01 22:51:35 +00:00
Mark Johnson f67f0a313d Preparing for getdown-1.2.4 release. 2012-06-01 22:48:35 +00:00
Mark Johnson c483b1dc64 - Let StatusPanel handle asyncronous loading of background images (ie: when in applet mode) 2012-06-01 22:47:00 +00:00
Michael Bayne 8fec356846 Handle java.home pointing to the JDK the JDK's JRE. 2012-05-01 20:30:34 +00:00
Mark Johnson c24abe2c7f Preparing for 1.3-SNAPSHOT development. 2012-04-04 03:31:04 +00:00
Mark Johnson 4f5e7049f3 Preparing for getdown-1.2.3 release. 2012-04-04 03:17:05 +00:00
Mark Johnson b022c03321 - reinit the play again button before displaying since the image could have been a downloaded 
resource
 2012-03-30 22:35:27 +00:00
Mark Johnson 73d5bcb605 - Some tweaks to the play again button handling 
- Removed the very naughty interrupt swallowing used to detect if the process started correctly
under optimal arguments, replaced it with a busy-wait loop so the thread can still be used to
launch the application multiple times
 2012-03-30 03:33:51 +00:00
Mark Johnson ba86664122 - Added an optional play again button for the applet after getdown has launched the application 2012-03-29 23:13:51 +00:00
Mark Johnson aecd4ea650 Preparing for 1.3-SNAPSHOT development. 2012-03-22 01:22:16 +00:00
Mark Johnson 12b49f5b53 Preparing for getdown-1.2.2 release. 2012-03-22 01:16:24 +00:00
Ray Greenwell 6727e01625 Whoops, Throttle's reinit() is for changing the throttle parameters, 
not clearing the history of operations.
 2012-03-21 21:48:40 +00:00
Ray Greenwell 5a355460db French translations. 2012-03-18 17:37:40 +00:00
Ray Greenwell 268c327ebd Parse a background color from getdown.txt, or figure out a sensible one. 
Always fill the component with that, in case there's trouble with the
background image.
 2012-03-16 14:10:00 +00:00
Ray Greenwell dba65488f3 Clarify that we're trying to block div-by-0 by checking the totalsize. 
The elementSize can be 0, that's fine. It's when ALL the elements are 0....
 2012-03-16 14:08:10 +00:00
Ray Greenwell eb2fee6b7c - Right before we exit let's set the progress to 100% 
(launching normally stops at 99%)
- In the applet version's exit() we stop the 'throbber'.
 2012-03-15 22:47:49 +00:00
Ray Greenwell 828a4638b0 This might be causing a divide by 0 error because all the sizes are 0... 2012-03-15 21:34:32 +00:00
Ray Greenwell cbf49d87b8 Revamped German translations. 2012-03-15 18:17:09 +00:00
Ray Greenwell 358a14bdfa Spanish translations. 2012-03-15 06:32:08 +00:00
Mark Johnson 8d2db15433 Preparing for 1.3-SNAPSHOT development. 2012-03-15 01:26:02 +00:00
Mark Johnson 8003919d1d Preparing for getdown-1.2.1 release. 2012-03-15 01:24:10 +00:00
Ray Greenwell 5695bfdf9a Allow the arbitrary step percentages to be specified in getdown.txt. 2012-03-12 23:50:21 +00:00
Ray Greenwell 57242277c1 Start displaying progress at 0%, rather than 1%. 2012-03-12 22:56:03 +00:00
Ray Greenwell 2d89d7acf4 And fix this javadoc comment. 2012-03-12 22:41:29 +00:00
Ray Greenwell 19fa9b298e Revert to reporting global percent to setStatus(). 
The Getdown class can be extended with that method overridden,
so move the step->global calculation outside of it.
 2012-03-12 22:38:12 +00:00
Ray Greenwell a07bb6066b A hopefully kosher edit. 
This little chunk of code has been tweaked and cargo'd forward for years
with no documentation as to what's going on.

What I object to is the blatent disregarding of the width specified in
getdown.txt with something calculated internally. (width - x*2)

GIGO; fix your fucking getdown.txt.

- If we are not granted privileges, reading the metadata breaks, which
is why the fallback was first added.
- Later it was tweaked because getWidth() can sometimes report 0 and
that would cause the fallback width to be negative.
 2012-03-12 22:17:41 +00:00
Ray Greenwell 16017037e8 - Nixed the START step. 
- Allow multiple percentages to be specified for a step. The lowest one that's
  higher than the current percentage is used.
- It seems sometimes the UI is shown after some progress is made. Track
  the percentage we're at when the UI is shown and reset that to be the new
  0, scaling subsequent progress to fill the remainder.
  I added this convinced I needed it, but now I'm seeing that it's always
  at 0 when the UI is shown...
  Perhaps I'll revisit that after I do some other stuff...
 2012-03-12 21:52:15 +00:00
Ray Greenwell e025be1079 Scratch that. 2012-03-12 21:44:33 +00:00
Ray Greenwell be1385d634 Reinstate not bothering the parent observer if the size of the current 
element is 0.
 2012-03-12 21:30:07 +00:00
Ray Greenwell 0a6a46898a Remove ellipsis from the text for the Patch Notes button. 
Ellipses on buttons/menu items typically means "pressing this
will not invoke an action directly because more information/customization
is needed". For example the ubiquitous "Print..." displays a
printing dialog, it doesn't actually start printing.
 2012-03-08 22:05:30 +00:00
Ray Greenwell 40b593677b Let's start/stop the timer when the panel is added/removed. 2012-03-08 22:01:17 +00:00
Ray Greenwell cb995489b6 Remove ellipses from the translations for our steps, as that's now "throbbed". 
Japanese was using the unicode character for an ellipsis, that was removed too.
 2012-03-08 20:36:14 +00:00
Ray Greenwell 9fc677949a Add a bit of "throbbing" to the display by displaying 1, 2, or 3 dots 
after the status, incrementing every second.

Even if the status or percentage doesn't update for a while, the user
will know that the updater is still "working".
 2012-03-08 20:11:13 +00:00
Ray Greenwell c8e3318705 Another bugfix: There is code to smooth-out the reported time values, 
however nothing was reset between different phases reporting their
own independent time-remaining values.
 2012-03-08 19:04:52 +00:00
Ray Greenwell 4c94356981 Move the time-remaining display to the status area. 
This could cause problems but I believe that any time we display the
time remaining we are also showing a short status string.

Hand-massaged the translations, hopefully everything still makes sense
in each language.
 2012-03-08 18:57:54 +00:00
Ray Greenwell 42f14f9747 Rebalance the "final percentages" for the steps. 
In the end I may allow these to be specified in one's getdown.txt.
 2012-03-08 17:58:53 +00:00
Ray Greenwell 0d7cf4f67f I have no idea what the heck the MetaProgressObserver was doing, 
but it wasn't doing the right thing. Fixed it.

I honestly have no idea how this was working. Maybe it just wasn't.
Maybe we never noticed before because with the per-step progress
bars we weren't seeing it exceed 100 percent.

And then use that instead of the UnifiedProgressObserver I wrote,
before I saw MetaProgressObserver.
 2012-03-08 15:21:12 +00:00