From: brett l. <bre...@gm...> - 2011-10-19 16:00:15
|
Okay. Sounds like a fair bit of work to do, but very worthwhile. :-) ---Brett. On Wed, Oct 19, 2011 at 11:31 AM, Stefan Frey <ste...@we...> wrote: > Brett: > I had a first look into adding Java Webstart support for Rails and as > suspected there is an issue with the Classloader. Even if we provide a user > defined classloader it is not used in those cases where Rails uses the > Class.forName method to create new (18xx-game specific classes). This has to > replaced. > > Reference: > http://download.oracle.com/javase/1,5.0/docs/guide/javaws/developersguide/faq.html#211 > > In addition we have to make sure that all other resource files also get loaded > by the classloader from the jar. > > Except from that it is mainly an issue to write the ant-tasks for packaging a > jar for Rails only and then upload this and the library jars (after signing > them) to sourceforge. This can heavily automated by creating an ant task. > > As it still requires some code/build modifications I prefer to add that to the > to-do list for Rails 2.0 and have no intention to backport this to Rails 1.x. > > Stefan > > > On Monday, October 10, 2011 09:02:04 pm brett lentz wrote: >> I suspect it was my own lack of knowledge on the whole process. >> >> Our classloader (and hex drawing code) comes from the Colossus project >> ( http://colossus.sourceforge.net/ ), and they provide a JNLP. So, I >> doubt there's any technical blockers to providing one. >> >> ---Brett. >> >> On Mon, Oct 10, 2011 at 2:15 PM, Stefan Frey <ste...@we...> wrote: >> > Do you remember what the main obstacle was? I suspect the >> > custom made classloader? >> > >> > On Monday, October 10, 2011 08:05:20 pm brett lentz wrote: >> >> I looked at creating a JNLP several years ago, but couldn't really >> >> make heads or tails of the process. >> >> >> >> If you can make it happen, that'd be awesome. I'd love to have a link >> >> on the website that people can click on to launch the latest version >> >> of Rails. >> >> >> >> ---Brett. >> >> >> >> On Mon, Oct 10, 2011 at 2:01 PM, Stefan Frey <ste...@we...> wrote: >> >> > Erik: >> >> > you are right 1.5.1+ is correct, my train of thought got sidetracked. >> >> > >> >> > I was thinking about that too, as changing the version number is the >> >> > only remaining manual task to publish a new release. >> >> > >> >> > However there will always the need to update the wiki and html pages, >> >> > so it still requires manually intervention. >> >> > >> >> > I am considering adding webstart support (in addition to the file >> >> > releases - not as an replacement), but I want like to know the >> >> > opinions of the others about that? >> >> > >> >> > Stefan >> >> > >> >> >> I have no opinion on whether or not to put branches in the repo, as I >> >> >> ignore them all (so far). However, I would like to see a correct (if >> >> >> temporary) version number in the master Game.xml, so that the >> >> >> approximate version of saved files can be identified. In my opinion >> >> >> that should be 1.5.1+, literally: 1.5.1 and more. >> >> >> (A build number would be even better, once we have managed nightly or >> >> >> weekly builds. Would it be possible to have the code retrieve the >> >> >> latest commit hash?) >> >> >> >> >> >> Erik. >> >> >> >> >> >> >> >> >> |