Hey, thanks for asking. It took us some head-scratching to get to grips with this @appearance thingy... :-).
For one thing, the @appearance tags you currently find in the code are probably all outdated, and are not used anyway: http://bugzilla.qooxdoo.org/show_bug.cgi?id=4553 For each widget that uses it, you can find its default appearance id in its "appearance" property as its init value, so there is no need to document this in an additional @ tag (Although this should be mentioned somewhere in the docs and I'm not sure it is). For another thing, there *is* actually a use case for additionally documented appearance id's, which concerns child controls. If you want to custom-theme a widget which has child controls, those child controls often receive specific appearance id's from the parent, which you have to know in order to properly theme the child controls as well. These child control-specific appearance id's are currently only in the widget code, and should be lifted to the documentation of the parent widget. We're thinking about a way to achieve this. T. On 01/13/2011 10:32 AM, danovics wrote: > > I should be blind, but just couldn't find what is the @appearance key in the > api comment for. > E.g. qx.ui.table.rowrenderer.Default > Please tell me if you know... > Thanks > ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
