LDInspector

[N. W. Perry]

Speaking for Linux/MacOS versions: if your starter file changes the directory to the one the jar-file is in, you have to put your LDInspector.ldi there. But if you set all Java-paths correctly (which I have no idea for MacOS), you may start LDInspector from any directory and have another LDInspector.ldi in each one.

This worked very easily; I just put the .ldi file next to the .jar file in the same directory, and it started right up without complaint.

I am also not too sure how best to change Java paths, and not sure it's worth researching. As long as I have my starter file in the Applications folder (after all, it is itself an application), I have no trouble locating the program.

Maybe LDInspector could offer a command line option? Something like

Code:

java .... ldinsp.LDInspector -data PATH_AND_FILE.ldi

This would allow even for Windows to have multiple workspace configurations.

Shell I?

I can make it work either way, but that may well be useful to others. (For one thing, it would allow me to put my workspace back into the more logical Application Support directory, rather than deep in my system library where password authentication is required.)