| SWT AS JSR [message #280175] |
Mon, 31 January 2005 14:03  |
|
Originally posted by: denisw.online.de
Why don`t you recommend SWT as Java Standards Request? When the API gets
changed to have almost the same classes (and more), it would be a great
replacement for AWT. SWT would then be in a java.swt package, or in
java.awt as an "AWT 2.0". What about that?
|
|
|
|
|
|
|
| Re: SWT AS JSR [message #280251 is a reply to message #280222] |
Tue, 01 February 2005 09:44  |
|
Originally posted by: Chris_Laffra.ca.ibm.com
Funny. See http://www.eclipsefaq.org/chris/ under "standards".
--
Chris Laffra, http://eclipsefaq.org
"Ian Phillips" <ianp@ianp.org> wrote in message
news:ctmric$bs5$1@www.eclipse.org...
> > An what does it buy Java? It is terribly devisive already. What would be
> > gained?
>
> Probably the only thing that could be said to be gained from this would
> be if you were aiming for a shot at getting SWT included as a standard
> part of the J2SE release.
>
> That, and seeing flocks of pigs over Sun HQ of course...
|
|
|
|
| Re: SWT AS JSR [message #280339 is a reply to message #280175] |
Wed, 02 February 2005 03:00 |
 Robert Enyedi
Messages: 68
Registered: July 2009 |
Member |
|
|
Denis Washington wrote:
> Why don`t you recommend SWT as Java Standards Request? When the API gets
> changed to have almost the same classes (and more), it would be a great
> replacement for AWT. SWT would then be in a java.swt package, or in
> java.awt as an "AWT 2.0". What about that?
>
Before doing that, how about solving SWT's design and implementation
problems?
I think that what SWT does under the hood is just great. It's fast, has
a rich component set and is good looking. But, regarding it's API, some
parts of it are poorly designed. I'm talking about the constants inside
the huge SWT class (but only some constants made it there - see
GridData.FILL) and the inheritance issues. See the post from
http://javalobby.org/forums/thread.jspa?threadID=16852&t start=0
And parts of the implementation of SWT seem unfinished/hacked. For
instance, you can't have a button with both image and text. This is also
true for the label control, but there's a custom label control that has
both (no custom control for buttons). And when you set a button's image,
your button will no longer be consistent with the Windows XP theme (same
problem with buttons of SWT.ARROW type).
With Swing Sun didn't solve some tricky issues (in fact Swing is only
95% finished after 7 years of development), but such basic things were
solved right from the initial design.
So I hope that the people from the Eclipse SWT dev team aren't thinking
about standardization until problems like these aren't addressed...
|
|
|
| Re: SWT AS JSR [message #280420 is a reply to message #280339] |
Wed, 02 February 2005 22:40 |
|
Originally posted by: Chris_Laffra.ca.ibm.com
"Robert Enyedi" <renyedi@yahoo.com> wrote in message
news:ctq1ae$4ti$1@www.eclipse.org...
> So I hope that the people from the Eclipse SWT dev team aren't thinking
> about standardization until problems like these aren't addressed...
SWT is still evolving. Having performance as the main design
factor makes you choose certain tradeoffs that may come off
as inconsistencies or as things that are not well thought out.
To me personally, standardization makes sense when there are
multiple (competing/conflicting) implementations available
and customers need a standard to enforce stability in the
implementations. For SWT, there is only one provider, the
eclipse project, and there is little need for a standard (?).
Standards are very "expensive" to develop. You have
to ask yourself whether the benefits outweigh the costs.
If you see problems in SWT, please submit a PR and if
you have a solution, provide a patch with your bugzilla
report. Only when people help out can the eclipse team
solve all problems.
--
Chris Laffra, http://eclipsefaq.org
|
|
|
| Re: SWT AS JSR [message #280421 is a reply to message #280175] |
Wed, 02 February 2005 22:40 |
|
Originally posted by: Chris_Laffra.ca.ibm.com
I suggest you ask this question also at the eclipse.foundation newsgroup.
--
Chris Laffra, http://eclipsefaq.org
"Denis Washington" <denisw@online.de> wrote in message
news:ctlvdm$ri0$1@www.eclipse.org...
> Why don`t you recommend SWT as Java Standards Request? When the API gets
> changed to have almost the same classes (and more), it would be a great
> replacement for AWT. SWT would then be in a java.swt package, or in
> java.awt as an "AWT 2.0". What about that?
>
|
|
|
| Re: SWT AS JSR [message #280485 is a reply to message #280175] |
Fri, 04 February 2005 00:40 |
|
Originally posted by: bob.objfac.com
Oh s***. You've kicked off the SWT vs. AWT/Swing permathread.
Bob Foster
Denis Washington wrote:
> Why don`t you recommend SWT as Java Standards Request? When the API gets
> changed to have almost the same classes (and more), it would be a great
> replacement for AWT. SWT would then be in a java.swt package, or in
> java.awt as an "AWT 2.0". What about that?
>
|
|
|
Powered by
FUDForum. Page generated in 0.05680 seconds
] 
Search
Help
Register
Login
Home
