[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[news.eclipse.tools] Re: Why should I use SWT?
|
I don't know where the beginning of this thread went, I can't see it, so I'm
replying here:
The following statement is being made about Native Widgets in general, and
now SWT.
> >* Native widgets will always perform better than emulated ones. This is
> >most important in very small embedded environments.
This is not true. Look at the expense of updating a native Tree when you do
something like
change the attribute of a filter. You must update the tree with all of the
new TreeItems introduced
by the change. The number of updates is limitless, and although I'm sure
embedded environments are
a concern, so are large scale development applications. There may be
thousand of items to be inserted
into the Tree.
In Swing, the performance of the same update is bound to the portion of the
Tree that is visible.
JTree renders itself directly against a Model, which in this case may have
simply had a filter
flag changed. There is one "repaint" request, and there are no superfuous
animations or Scrollbar
spasms that result from inserting TreeItems in a native Tree.