May this wasn't clear enough. I meant creating a new appearance theme instead of modifying a existing theme. I don't mean the appearance entry but the whole theme. It's IMHO a bad idea to modify an object after it's creation. Better would be to define an own appearance theme and use this theme e.g. my.themes.AppearanceTheme.
Cheers, Sebastian dperez schrieb: > > I agree with you in many cases, like a widget that I want a special > appearance. > But some other cases, like for example, changing the focus highlight for ALL > TextFields, it is more practical to change the textfield appearance, instead > of creating a new one. > The cause of this, is that text fields are used inside ComboBoxes, Spinners > and some other components, and I would need to set a new appearance for > every used TextField. > That's why my example modifies the appearance. > > > Sebastian Werner wrote: >> IMHO, the documentation does not follow the way to go. It's better to >> define an own separate appearance theme and not to modify the existing >> one. >> >> Try your look with inheritance and configure the default appearance >> theme afterwards would be IMHO the better way. >> > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
