Re: Running AppleCommander GUI?

[Rob <robgreene@users.sourceforge.net>]

schmidtd <schmidtd@my-deja.com> wrote in
1c677999-d039-430f-92e3-6a90eac28221@x38g2000pri.googlegroups.com:">news:1c677999-d039-430f-92e3-6a90eac28221@x38g2000pri.googlegroups.com: 

> On May 26, 10:52�am, Steven Hirsch <snhir...@gmail.com> wrote:
>> First, a disclaimer: �I do not like Java.
> 
> Yes, yes.
> 
>> Does anyone know the magic incantation for getting the GUI up on
>> Linux? 
> 
> There's a reason Rob bundled AppleCommander into an executable on
> Windows and an app on Mac.  And there's a reason why I hide the Java
> command line of ADTPro behind a script for Unix-alikes.  It's
> complicated.
> 
> First, give full qualification to the jars you need.  The classpath,
> or -cp command line switch will do that for you:
> 
> -cp /usr/lib/java/swt-gtk-3.5.1.jar:/wherever/AppleCommander-1.3.5.jar
> 
> But then you also need to pull the main class out of the manifest;
> that is: com.webcodepro.applecommander.ui.AppleCommander
> 
> Then, there are some native libraries for SWT too, aren't there?
> There are on Windows and Mac.  For those, you need to give the -
> Djava.library.path= command line switch, and point to those, too.
> 
> So I can get you as far as that - there's still the issue of 64-bit
> SWT native libraries, which I trust you know where are.  A full
> invocation might look like this:
> 
> java -Djava.library.path=/path/to/SWT/jnilibs -cp /usr/lib/java/swt-
> gtk-3.5.1.jar:/wherever/AppleCommander-1.3.5.jar
> com.webcodepro.applecommander.ui.AppleCommander -swt
> 
> (I'm unsure if the -swt switch is passed in - or if Java will consume
> it.)

I've been lurking but not doing too much.  I'll throw in a pitch though
-- 

My UI sucks.  There, it's been said.  :-)

Anyone interested in redoing it -- with Swing so it works out of the
box?  At the time I was writing this, Swing performance was less than
ideal, and SWT seemed the way to go... plus I was doing it for my own
edification. 

Another option is to use something like OneJar which I've discovered
relatively recently -- and it's supposed to be able to handle JNI too. 

I believe the one issue I wasn't able to resolve was the default JVM max
memory usage of 64MB -- not sure where that stands today... -Rob