Re: Why Use Thinlets? Why Build Your UIs Using XML?

ThinletConstants: it's simple to create the source of this file using
Thinlet's 'dtd' field. it should be separated from Thinlet source, either a
class including static final strings or an interface, probably the later is
better, thus you could omit the ThinletConstants prefix in your source.

Object Thinlet Wrapper:  some time ago I wrote a simple application to
create those sources automatically from Thinlet's 'dtd' field to measure its
jar size, it creates the majority of the sources.

DTD: please add the modified one to the CVS and I'll create a new zip file
for download if required.

Validators: maxlength property is nice, but probably the list of validators
is longer (integer, decimal including iternationalized symbols, max value,
date, after today, required, min length, cardnumber, accountnumber with
checkdigit, etc.). Maybe I'll try to create a demo similar to jgoodies.com's
one. Probably textfield's insert and remove listeners are sufficients for a
common validation framework, probably these listeners methods should return
e.g. false boolean value to ignore e.g. a letter character in decimal fied.

Datepicker: it is a very complex widget including a filtered textfields,
up/dow spin-buttons, and a popup chooser. It's a nice task to collect
Thinlet's methods should be protected to allow this extension.

Why Use Thinlets: it is useful for web browsers, much more interactive than
HTML+JavaScript and the application code is very simple, although I can't
suggest it compared to Java Web Start if it was available. And Thinlet is
ideal for Personal Java (e.g. PDAs) where AWT has a limited widget set and
other toolkits are commercial or GPL licensed.