Re: [ jEdit-devel ] jEdit launcher

[Slava P. <sl...@je...>]

On Tue, May 08, 2001 at 04:39:40AM -0400, root wrote:
> That's fine.  If the goal is a single installation program, perhaps the Windows
> installation routine should be performed using a JNI call to a dll file, rather
> than having an executable that someone might try to run alone.  That way the
> Windows installation could not be performed outside of the Java installer without
> a good deal of hacking.  The other advantage is that the choices in the Java
> options combo box can be set dynamically to take into account the location of
> jEdit.jar

I don't understand. It would be easier, both for me, because I wouldn't
have to worry about keeping the interfaces stable for the sake of JNI,
and for you, because you wouldn't have to write JNI stubs, if the
installer just unpacked an install.exe, ran it with the appropriate
parameters, then deleted it.

> I shall make it so.  What about uninstall deleteing the jEdit files as well?

Good idea. Why don't we go all the way and register jEdit as an
application in the 'Add/Remove Programs' control panel as well?

> You should reconsider this.  If I were asked to choose between jEditLauncher and
> wheelmouse capability, I would choose wheelmouse.  If jEdit were an automobile,
> jEditLauncher would be a bigger engine and the wheelmouse would be power
> steering.  The latter is more important, and it would be odd to make it optional
> in a Windows installation package.

Automobile analogies suck. jEdit should include as little native code
as possible. Maybe when Java 1.4 is released, a wheel mouse plugin
will be included with the core (using the Java 1.4 wheel mouse API).

Slava