Re: [Openjnlp-devel] Arg...

[Kevin H. <ke...@na...>]

On Monday, March 25, 2002, at 09:25 , Christopher Heiny wrote:
[...]
> development).  However, over the next few days I hope to be able to put 
> in
> some effort, and plan to look into the following things (in part to 
> keep the

Yikes. I just did a whole bunch of changes to the launching process to 
support command-line operation. I needed stuff in openjnlp-lib which I 
just got working last night. I'll be committing the changes later today.

[...]
> 	- A "--gui/-g" command line option which will pop up the GUI and 
> open the
> specified file/URL.  F'rinstance:
> 		openjnlp --gui http://www.here.com/there.jnlp
> Will pop-up the console, fetch the JNLP file, and then start the app.  
> The
> GUI will hang around after the launch for further JNLP fun.

The main entry point for OpenJNLP (org.nanode.app.OpenJNLP) is the 
GUI-based application. I believe the GUI coming up should be the default 
behavior, maybe a -nogui option makes more sense.

> 	- When openjnlp is launched, look for one on the local machine 
> with the same
> user (and under X, the same display), and have that one perform the 
> requested
> tasks instead.

This sounds like some IPC between running instances of OpenJNLP, how 
would this work? On Mac OS it is possible to send 'odoc' events to tell 
a running app to open a document, but how would this be implemented in 
java on Windows and linux?

I will be following this message up with a separate message dedicated to 
command-line launching so we can all get a good handle on how we want 
OpenJNLP to work.