[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: RE: [platform-swt-dev] org.eclipse.swt.SWT
|
was sufficient performance tests done to validate whether the performance
bottleneck is indeed the getters-setters? and won't method inlining by
compilers solve this to some extend?
Veronika_Irvine@xxxxxx.
com To: platform-swt-dev@xxxxxxxxxxx
Sent by: cc:
platform-swt-dev-admin@ Subject: RE: RE: [platform-swt-dev]
eclipse.org org.eclipse.swt.SWT
02/27/2003 05:27 PM
Please respond to
platform-swt-dev
When a setter/getter is provided, it implies that calling that method will
cause something to take effect immediately. The use of public fields in
GridData and GridLayout is deliberate. In most cases, the application
will update several fields and then to have the changes take effect they
must call layout. Since laying out widgets is expensive and can result in
flash, you do not want to change each little thing one at a time and cause
a layout to occur each time. This is a general design philosophy in SWT,
not an oversight.
"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: platform-swt-dev-admin@xxxxxxxxxxx
02/27/2003 11:33 AM
Please respond to platform-swt-dev
To: <platform-swt-dev@xxxxxxxxxxx>
cc:
Subject: RE: RE: [platform-swt-dev] org.eclipse.swt.SWT
>> From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
>>
>> The Javadoc for SWT is abysmal.
> From: Mike_Wilson@xxxxxxxxxx
>
> As one of the authors of the existing SWT javadoc, I'd have to say I
agree.
Ah, it's not so bad, Mike. Really, after doing some serious looking, I
realize that some areas need more meat is all. And as you say, the
feature
set is not yet complete, which is what I pretty much thought.
In fact, that's my feeling on SWT in general. It's just not quite soup
yet.
It's like you're adding things at a great clip, with the intent to go back
and clean things up. As an example, the lack of setters and getters in
GridData as opposed to the consistent use of setters and getters in the
widget classes is a little confusing. One of the great things about Swing
is that the methods are remarkably consistent throughout the packages.
There seems to be a little less of that structure in the SWT classes,
especially some of the more advanced stuff (like the layouts).
Just my .02
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev
