[news.eclipse.platform.swt] Re: re-write versus port decision, Swing

[marco_m_jain@xxxxxxxxxxx (marco jain)]

thanks for the responses guys.  I have to say that deciding on the right
approach for this isn't easy.

does anyone have any comments that they could share on the other set of
questions in the original post which has to do with the swing in-process
option?

thanks again,
-marco.

Steve Northover wrote:

> We are looking into it.  Implementing AWT in SWT doesn't seem like the right
> way to go because of  things like Java2D.

> "ted stockwell" <ted.stockwell@xxxxxxxxxx> wrote in message
> news:bertfl$ks$1@xxxxxxxxxxxxxx
> >
> > "marco jain" <marco_m_jain@xxxxxxxxxxx> wrote in message
> > news:ben1fe$cu0$1@xxxxxxxxxxxxxx
> > >
> > >  I haven't seen
> > > it in eclipse release 2.1 or 3.0 plans.  i'm looking for a bridge that
> > > would be a stable and supported production version.
> > >
> >
> > 'Provide Swing interoperability' is an item on the 3.0 plan for SWT, see
> >
> http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/R3_0/p
> > lan.html#Overall_Plan.  This item is currently under investigation.
> >
> > I sure would like to hear from the SWT team about thier plans or possible
> > approaches for Swing integration and how the limitations of the current
> > AWT_SWT approach will be addressed. I would especially like to know if the
> > approach of implementing an AWT Toolkit using SWT has been considered and
> if
> > anybody is working on that.
> >
> > Thanks,
> > ted stockwell
> >
> >