Hi, > Hi, > >>> The problem with Webstart is, that the >>> classpath is only the jre/lib/deploy.jar. So we cannot load readme.txt >>> from classpath :-( >>> >> are you sure there is no way for a webstart application to load a file >> either from a webserver or from an external archive? >> > Cannot understand why the file could not be in the path (in the jar) > I cannot found a possibility to load such configuration files automatically :-( You can only define the JAR's. For the default-plugins.xml file i manually download the file to system tmpdir. The file location i surrender the "-default-plugins" commandline option. This is ok, but the readme.txt wil be loaded from the classpath. As i have written above, the classpath of a JWS application is the deploy.jar. I think that the deploy.jar handles the classloading stuff for a JWS application. This JWS behaviour was new for me too. >>> In principle we should change both, the loading and the content of the >>> readme.txt! >>> 1. There are too many unimportant and not (end)user suitable informations. >>> >> could you name one? some of it might not be needed on a day to day basis but >> essentially all of it is enduser information. >> > Agree with Matthias on this point (also agreed with Ede for "one place > to maintain > all the infos"). > The "one place to maintain" is an argument, ede. > Hmm embarassing. > The about panel mixes nice looking logo + software version on the top, > with rough text area containing unreadable license information (sorry Ede, > information is important, just unreadable for most normal people ;-). > Most information is formal but useless at this point (how to start the > application) and it does not always fit well the software version (PLUS > vs CORE). > This is what I mean. > I have two suggestions to improve it (but it has a very low priority for > me) : > - let only the logo + version + general license (+ date ?) in the about > panel > and add a button to call explicitly the readme file which will be > opened in its > own window > - html-ize the readme file (so that it can be beautified) and put it in > its own tab > > What do you think ? > A very good suggestion to split this informations. And the html-ize readme is good for external translators. Such as the help for the keyboard shortcuts. For better JWS support i would change the loading mechanism, so that this files can be loaded from local filesystem or from a webserver. From every URL, local or remote. >>> 2. I prefer translated text's within the language directory. >>> >> i would to if there were people maintaining these when the infos change. >> > I think that having them in the jar is not user-friendly for > non-programmers doing translations > BUT, it encourages people to contribute their translation to the project. > Just my feeling, > >>> 3. The "about text" should contain a small description, contributors and >>> licence information. >>> >> same as above. that's why i put the readme there. one place to maintain all >> the infos. >> > See above. > >>> 4. White text background and grey panel background is a little bit ugly. >>> >> i like it. it hint's that the file is actually not part the gui itself. >> > See above. > > Michaël > >> ..ede >>
Matthias -- _ __ ___ _________________________________ ___ __ _ Technologieconsulting Matthias Scholz Siebigeröder Str 17a 06308 Klostermansfeld T +49 34772 34150 E m...@jammerhund.de W www.openjump.de _ __ ___ _________________________________ ___ __ _ ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
