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

From: "Robert Bajzat" <robert.bajzat <at> thinlet.com>
> 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.

I would suggest a class is a better choice. By making Thinlet implement
ThinletConstants you require ThinletConstants at RUNTIME. If it is a class,
then the constants are copied to Thinlet.class at COMPILE time, so there is
no need to include ThinletConstants in the jar.

> 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.
It has use as an additional jar for people who don't care so much about
download size.

> 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