Re: AppleCommander bugs and glitches

["John B. Matthews" <nospam@nospam.invalid>]

In article <nKqdnVeGlcgkSnnQnZ2dnUVZ_jGdnZ2d@giganews.com>,
 Steven Hirsch <snhirsch@gmail.com> wrote:

> On 05/30/2011 07:07 PM, John B. Matthews wrote:
> > In article<-tqdnfWxvJdQKH7QnZ2dnUVZ_vadnZ2d@giganews.com>,
> >   Steven Hirsch<snhirsch@gmail.com>  wrote:
> [...]
> I don't think you need a development environment, just a linux VM 
> with java runtime and the swt libs. For Ubuntu, the packages are:
> 
> openjdk-6-jre
> openjdk-6-jre-lib
> libswt-gtk-3.5-java
> libswt-gtk-3.5-jni
> 
> (not even sure all of the above are required, but I didn't want to 
> uninstall things just to find out)

Ah, thanks; that's what I wasn't sure about. I had the first two, and 
the other two are mutually dependent. Your launch script is perfect. Now 
I can see what you meant about having to select file types. On Mac OS, 
the drop-down list never even appears, and all files are selectable.

> My system is 64-bit.
> 
> > As an aside, I used your method to launch AppleCommander from the Mac OS
> > command line, and it exhibited the same hang-on-exit anomaly reported
> > here earlier. I suspect I've run afoul of the 32- to 64-bit transition,
> > but the result is illuminating. Thanks. For reference:
> >
> > cd AppleCommander.app/Contents/Resources/Java
> > java -d32 -XstartOnFirstThread -Dswt.library.path=. \
> >      -cp .:swt.jar:AppleCommander.jar \
> >      com.webcodepro.applecommander.ui.AppleCommander
> 
> 64-bit vs. 32-bit? So much for "write once, run anywhere"...
> 
> FWIW, I have never seen AC hang on exit.  There really _isn't_ a 
> direct means to exit, however, is there?  I always close it by 
> destroying the window with a click on the "X" button.

Same for me. On Mac, opening anything later hangs on exit; I'm still 
trying to figure out why.

-- 
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>