| Can't wait!!!!!! [message #4074] |
Sat, 03 June 2006 21:41  |
Eclipse User |
|
|
|
Originally posted by: jamesdcarroll.hotmaill.com
Can't wait for the inevitable time in the future that folks complain that
the non native SWT classes that Nebula will create are fat and slow?
Does no one remember that we've already gone through this with Sun and the
AWT to SWING process?
|
|
|
|
|
|
|
|
| Re: Can't wait!!!!!! [message #562018 is a reply to message #4074] |
Sat, 03 June 2006 23:23  |
| Eclipse User |
|
|
|
James D Carroll wrote:
> Can't wait for the inevitable time in the future that folks complain that
> the non native SWT classes that Nebula will create are fat and slow?
>
> Does no one remember that we've already gone through this with Sun and the
> AWT to SWING process?
Not every Nebula control will be this way. :-)
You might want to try CompositeTable, which I submitted to Nebula on one
of the first days possible. You can find more information about it in
the mailing list archives, but the gist is the following:
Table control:
- Each row in the table is a Composite that you create.
- Your row objects are encouraged to contain native controls as much as
possible.
- Fully virtual: only creates row Composites for rows that are visible
and only fetches model objects for rows that are visible
Result: it's easy to make a grid with full in-place editing that looks
and feels as close to native as possible because the in-place editing
part really *is* native.
A side effect is that it's really fast.
To find CompositeTable:
CVS server: dev.eclipse.org
Root: /home/eclipse
Project: org.eclipse.jface.examples.databinding
The latest code as of today is in the 3.2-lockdown branch--the
development branch we created when the code base went into lockdown mode
for the 3.2 release. This coming week, we expect to merge back with
HEAD when Platform moves to the 3.3 development stream.
Best Regards,
Dave Orme
Visual Editor Project Lead
Eclipse Platform Committer on JFace Data Binding
|
|
|
| Re: Can't wait!!!!!! [message #562042 is a reply to message #4074] |
Tue, 06 June 2006 12:51 |
| Eclipse User |
|
|
|
A solitary custom widget, in-and-of itself, does not have to be fat and
slow. Hopefully Nebula widgets will be high quality.
Its important to remember that Nebula isn't attempting to redefine the
basic widgets which typically have native peers. I would highly suggest
that if you need a widget, use the native SWT widgets. If your needs
aren't met by the standard SWT widgets, then explore Nebula.
-Chris
James D Carroll wrote:
> Can't wait for the inevitable time in the future that folks complain that
> the non native SWT classes that Nebula will create are fat and slow?
>
> Does no one remember that we've already gone through this with Sun and the
> AWT to SWING process?
>
>
>
|
|
|
|
| Re: Can't wait!!!!!! [message #562127 is a reply to message #4074] |
Fri, 09 June 2006 13:13 |
| Eclipse User |
|
|
|
I would also point out, as chris has eluded too already, that the nebula
project adds choices for developers. When we have an array of styles to
chose from we can make better products, we just need to be cognizant of the
impact of our choices and make informed descisions that satisfy our
requirements, whatever they may be.
-spencer
"James D Carroll" <jamesdcarroll@hotmaill.com> wrote in message
news:e5tdlu$rb2$1@utils.eclipse.org...
> Can't wait for the inevitable time in the future that folks complain that
> the non native SWT classes that Nebula will create are fat and slow?
>
> Does no one remember that we've already gone through this with Sun and the
> AWT to SWING process?
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.38870 seconds
Home