Quoting Matthew Sackman <[email protected]>:
> > These are hard. Getting the list probably involves trawling the docs on
> > msdn, adc, motif, qt, gtk, et al.
>
> This has already been done at least 3 times for Java so whilst you may
> or may not hate Java, the easiest solution is to look at the widgets
> they've implemented there.
<snip>
I hate it when I'm forced to program in Java. Sometimes I choose to for my own
mysterious reasons.
The AWT/Swing/SWT lists will give me all the widgets that need to be there
before we can call it v1.0, but the harder problem would still remain:
We need to determine the optimum set of sub-widget elements which we need to
implement as themable things. You need to be able to build every conceivable
widget from these blocks. That way you don't write a theme for buttons, but a
theme for "surface which you can click to do something" and for "tex which is
going to be used to label something". Since a button is composed of these 2
things it's pretty much the same amount of work either way. However, when a
new type of widget comes along we won't want to have to go and augment our
theme so it knows how to draw that new widget -- since it will be composed of
elements we're already familiar with.
It may well be that the elements you need in order to draw every swing widget
are sufficient for every other conceivable widget, but I'm not convinced...
I think the best course of action is to implement enough elements that we can
build all the v1.0 widgets, then go looking for widgets we couldn't implement
among the less-common sources.
Phil
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.