The main difference between the JavaPortablizer on the Portable page and the one at is that the one on the Portable page specifies a path relative to where the PortableAppsPlatform.exe (or menu) is stored, where the dreasmincode one tells you to put it anywhere. Compiling the launcher with NSIS is pretty easy, once you get all the required plugins added to the NSIS install. The source code of the launcher is included with the package if you'd like to tell it to look somewhere else first for a JRE/JVM, it's probably just a small change to the source code. In particular, if javaw.exe is found in PortableApps\CommonFiles\Java\bin, it will be used. If by chance the "kind of like this page" kind of looks the same as the portablized Java described above, jEdit will find and use it otherwise it will try to use a Java that is installed on the host computer in a more conventional way. (Unfortunately some programs, like FireFox, insist on looking in the host computer's registry to find Java, and the Java portablizer doesn't mess with the registry, so those programs probably won't use the portablized Java - but they probably won't find it with dreamincode's setup either.) It's set up so you only have to install Java once on your portable drive, and all such programs (including ) will find and use it. The description there is generic for any program that wants to use Java, and doesn't require you to install first. The Java Portablizer described for Portable doesn't require that is installed. jedit directory is cross platform as well. The jar files are cross platform (as far as I know), and the data stored in the. jedit directory in the right place on the USB drive, that would be be most of what you are talking about. Next time I have some quality time with a Linux box I'll experiment and see if I can come up with something.īottom line: if one makes a shell script to parse out the paths, launch java and tell it to look for the. There's the other tricks too, such as getting around the FAT32 filesystem on the USB drive, which might not mark things as executable. So you'd need a shell script that was able to parse out the correct directory/path and substitute it in the right place, or use relative paths that worked consistently. The main trick would be that the USB drive might not be mounted at the same point on different linux machines, so an absolute path might not work. PortableApps/jEditPortable/App/Jedit/jedit.jar, that should do it. If you can set up a shell script to launch whatever java runtime is available on the linux box, with the -D command line option pointing to the USB drive instead of ~/, and -jar pointing to the jedit.jar file on the USB drive at. The main trick the launcher uses is to call java(w) with a -D command line option, specifically ="$SETTINGSDIRECTORY" as well as -jar "$PROGRAMDIRECTORY\$". (It might under Wine, but I'm not sure why you would want to.) One particular consideration is that the launcher won't work as a native application under Linux. jedit directory to the place you mention, in the. JEdit Portable uses a windows launcher to start the program in such a way that it uses a Java runtime found on the USB drive (in the place set up for ), and redirects the. "C:\Documents and Settings\Scrape\.jedit" (or maybe in AppDir, it doesn't matter). jedit directory is normally found in Documents and Settings, e.g. jedit directory is normally found in the home directory (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |