MDI version, especially for Mac users of this app. However I do think
of ImageJ and Bob's solution seems a pretty good one. I don't like the
> I have also made some changes to ImageJ to allow a single pane for all
> windows, although I used a tabbed pane instead of MDI. Also, I tried
> to minimally change the base ImageJ classes such that the jdk 1.1 AWT
> UI still works.
> Key changes I made to ImageJ:
> * Add/Use IJ.getAppFrame() instead of IJ.getInstance() as the frame
> showing isn't the ImageJ instance for Swing (it's a JFrame).
> * A few changes to Toolbar,ImageWindow,ImageCanvas,ImageJ to use
> another UI framework for display (don't show the AWT UI).
> * Menus -- static methods need to be wrapped to call the singleton
> Menus instance (which may be a derived class, i.e. another UI framework).
>
> I'm not sure what the interest might be, but you can have a look
> (applet links) at
>
http://home.blarg.net/~bobcat/ImageJ/index.html>
> Note I used the swixml XUL engine to create much of the Swing UI (e.g.
> menus, toolbar), meaning you could create your own customized UI by
> using a different XML file.
>
> If there is interest in making the core ImageJ changes I could merge
> in the latest ImageJ version and provide my changes to Wayne.
>
> Thanks,
> Bob Curley
>
> Damien Farrell wrote:
>
>> Hi
>>
>> Anyone interested in the development of a version of ImageJ that uses
>> a single Swing desktop pane for all windows. Thought it might be a
>> useful alternative that could eventually be integrated into ImageJ
>> proper in some future version.
>> Anyone interested in this being developed further? I don't see any
>> major obstacles to it as yet. I made a preliminary version that seems
>> to work for most purposes, though many plugins will not currently
>> work.The ij.jar file and further info can be found at
>>
http://homepage.ntlworld.com/jfarrell/imagejmdi/>>
>> PS. If trying this out don't overwrite your old ij.jar, make a backup
>> copy first.
>>
>>
>> regards
>>
>> Damien Farrell
>>
>>
>
>