argument to class main() or a new "launcher options" element?

[olagarde]

Launcher Version: 1.0.1.3

Operating System: RHEL5 Linux 2.6.18-194.8.1.el5PAE and OSX10.7.4 Darwin 11.4.0

Java Version: 1.6.0_33

Antivirus Program:

Description of Problem:

Please excuse language failure, am C and perl, not java. Also unsure where to put feature request so here it goes, please correct if this is wrong....

Feature request: for installation directory in PlatformUtils.class, id 020 offset 0x0001244, please advertise argument to main class so that location can be runtime changed like "java -Xmx1024m -jar {launcher JAR} {installdirtag}={installdir}", or add widgetry to launcher option panel to do same?

Error Messages:

Error Log:

[olagarde]

Lacking source to PlatformUtils (and lazy admittedly) I have tried an obvious experiment, made a test jar with appropriate ".techniclauncher" binary-replaced with ".", space-padded to enforce UTF8 const pool integrity. Launched and ran fine in original "~/.techniclauncher" location, though now install directory ".techniclauncher" does not exist jar file? Then noticed network.

Disconnected network, launcher hung before presenting login panel as expected, "~/.techniclauncher" not created or existing. Started strace (-fFvp) on re-launched child and reconnected network, launcher immediately proceeded as expected. Directory "~/.techniclauncher" is created with timestamp of network stack and route table update on network reconnect. Output of strace on re-launch of jar per manifest.mf mainclass implies that network comms is informing install location. True or bad guess?

Please allow me a clarification: my goal is to have sweet Launcher update capability but also have Technic installs be self-contained and/or relocatable. Enforced common install directory makes very cumbersome to have multiple different-version technic instances concurrent. Makes side-by-side comparison of two Technic trees with different mod/content on one system very inconvenient. Configurable install directory makes installing, backing up, and testing multiple versions of launcher, technic, mod collections, etc., quite trivial, just operations on file trees really.

[olagarde]

BTY, sorry mind not on what I am doing. Modified jar is launched with script which wraps java within pushd/popd to unique directory, immediate goal is to have launcher file tree created within that unique directory instead of always within "~/.techniclauncher". Linking and/or mount encapsulation would move the install directory, but there would still only be *one* install directory. Or just say "go make your own", if I could take source and develop myself this too is I suppose a valid answer.