Re: Potential solution for conversion from AWT to Swing

Posted by Raymond Martin-2 on Dec 05, 2009; 3:51pm
URL: http://imagej.273.s1.nabble.com/ImageJ-development-involvement-contributions-tp3690030p3690084.html

Hi,

> > In running that plugin I have discovered a typical problem that occurs
> > in Java GUI applications, that of the GUI blocking during long running
> > processes. I have solved this in other GUI applications I work on by
> > using a specific threading library, Foxtrot(BSD license), that enables
> > the use of both synchronous and asynchronous threads in flexible ways.
> > SwingWorker can also be used to prevent the GUI freeze, but is not as
> > flexible (license?).
> >
> > Would adding this dependency be acceptable for the problem it solves?
>
> We usually prefer just to use threads.

You can, but using one of these solutions amounts to the same thing without
the work. These libraries just wrap threading code you would end up having to
write anyway, and then some. So why bother trying to manage threads when
someone else has done specific (high-quality) work to handle it properly?

> > Other than that, I have not run into any serious problems converting to
> > Swing yet. Since the potential for problems is believed to rest with
> > supporting plugins, would ask others to please point out, if they can,
> > exactly which plugins gave problems in past efforts to do what I am
> > attempting.
>
> Maybe you can provide your version so people can actually test out?  The
> most problems are actually with closed-source cannot-give-away plugins,
> after all.

Where can I post it for general access?

Regards,

Raymond