[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: RE: [platform-swt-dev] org.eclipse.swt.SWT
|
yes. but you are developing a toolkit thats going to stay for a long time.
next year, i percieve that cell phones woulf have double the storage
capacity. so don't you think that its better to get a good set of running
api's instead of worrying too much about storage capacity?
Randy Hudson
<hudsonr@xxxxxxxxxx> 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 08:30 PM
Please respond to
platform-swt-dev
If you look at many of the deviations from "accepted OO design", you will
see that they result in a smaller bytecode and a smaller runtime Jar. SWT
runs on Windows CE, maybe even a few cellphones out there are running SWT.
The fewer KB, the better (for embedded clients).
"Joe Pluta"
<joepluta@xxxxxxxxxxxxxxxxx> To:
Sent by: <platform-swt-dev@xxxxxxxxxxx>
platform-swt-dev-admin@eclips cc:
e.org Subject: RE: RE:
[platform-swt-dev] org.eclipse.swt.SWT
02/27/2003 02:39 PM
Please respond to
platform-swt-dev
> From: Veronika_Irvine@xxxxxxxxxx
>
> You disagree with our philosophy and that is fine.
I think (in my opinion) your design philosophy differs with accepted OO
design, which confuses me. This is not my personal philosophy, it's just
what I've read in every OO design methodology text I've ever seen. I'd be
interested to see something that suggests that public attributes are a good
thing.
> However, if you
> understand the philosophy you will see that it is actually applied
> meticulously within SWT.
When does setText in a label take effect? As far as I can tell, not until
you do a call to layout. Or am I mistaken in this?
> We chose to make it easy to distinguish when
> things are done immediately and when an additional step is
> required. Using
> getters/setters in GridData will result in a loss of information which
> will have to be captured instead in Javadoc.
This is another pretty bad argument, if you think about it. Because this
is
exactly the kind of information that SHOULD be in Javadoc, not in some sort
of "understood" internal design philosophy. Where exactly in the SWT
documentation does it state this design philosophy? How does a new SWT
programmer learn this? Or is it just something you decided on amongst
yourselves, regardless of the accepted conventions of design, and pass on
to
programmers through experience?
It's an interesting concept, but since it directly opposes convential
wisdom, is not documented, and is not strictly enforced, it's unlikely to
be
intuitive to newcomers.
Joe
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev
