Whatever we do we need to be backward compatible because there are a lot
of skins out there, and we don't want to break them.
We should start first on all the clean up code, like getting rid of the
XSS code. We need to convert the current XSS into CSS and to do that,
we'll need to make sure all the features that are in XSS are in CSS.
Jeanne
Andrew Robinson wrote, On 12/5/2008 7:33 AM PT:
All other frameworks use
component attributes for this, but Trinidad puts it in these
non-intuitive skinning keys.
Sorry, had one more comment right after I hit send again. Maybe just
having default component attributes for a web app would satisfy the
need. Like a way to say 'partialSumbit' should be defaulted to true on
all tr:commandLink. Then all the skin properties could be converted to
attributes and have their defaults set in a common location (like what
the skin does).
This would be much more useful and flexible as then page developers
can make exceptions to the rule.
