|
| Re: What about SWTSwing and Eclipse on Swing [message #1375 is a reply to message #1368] |
Mon, 20 August 2007 10:51  |
Eclipse User |
|
|
|
Well, there are (at least) three approaches to the general problem.
1) Create a port of SWT on top of Swing (SWTSwing and EOS)
2) Create a port of Swing on top of SWT (SwingWT)
3) Build on the SWT/AWT bridge so that apps on both toolkits can coexist
better (Albireo)
All three approaches have their merits. For me, the advantage of option
3 is that we:
* Keep the benefits of the native widgets from SWT for most of the
application while still using Swing where it is necessary.
* Don't need to modify the Swing components at all
So, that's why option 3 is the right choice for many applications. The
Albireo proposal was written with those requirements in mind. That's not
to say that the other options aren't the right choice in other cases.
As to whether Albireo should also include work on option 1 and/or 2 as
well as option 3... I suppose it could, but what would be the benefits
to combining the efforts? I don't see any obvious synergy among the
different approaches. But I'm curious to hear what others think...
Albert Strasheim wrote:
> Hello all
>
> I was wondering how the Albireo project relates to the work that has
> been done on SWTSwing and Eclipse on Swing?
>
> http://eos.sourceforge.net/
> http://swtswing.sourceforge.net/main/index.html
>
> It would be great if the work that has been done there could also be
> incorporated into Eclipse, in addition to improving the SWT_AWT bridge.
>
> Regards,
>
> Albert Strasheim
>
>
>
|
|
|
| Re: What about SWTSwing and Eclipse on Swing [message #572163 is a reply to message #1368] |
Mon, 20 August 2007 10:51 |
| Eclipse User |
|
|
|
Well, there are (at least) three approaches to the general problem.
1) Create a port of SWT on top of Swing (SWTSwing and EOS)
2) Create a port of Swing on top of SWT (SwingWT)
3) Build on the SWT/AWT bridge so that apps on both toolkits can coexist
better (Albireo)
All three approaches have their merits. For me, the advantage of option
3 is that we:
* Keep the benefits of the native widgets from SWT for most of the
application while still using Swing where it is necessary.
* Don't need to modify the Swing components at all
So, that's why option 3 is the right choice for many applications. The
Albireo proposal was written with those requirements in mind. That's not
to say that the other options aren't the right choice in other cases.
As to whether Albireo should also include work on option 1 and/or 2 as
well as option 3... I suppose it could, but what would be the benefits
to combining the efforts? I don't see any obvious synergy among the
different approaches. But I'm curious to hear what others think...
Albert Strasheim wrote:
> Hello all
>
> I was wondering how the Albireo project relates to the work that has
> been done on SWTSwing and Eclipse on Swing?
>
> http://eos.sourceforge.net/
> http://swtswing.sourceforge.net/main/index.html
>
> It would be great if the work that has been done there could also be
> incorporated into Eclipse, in addition to improving the SWT_AWT bridge.
>
> Regards,
>
> Albert Strasheim
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04261 seconds
Home