Hugh Gibson schrieb: > The API documentation system doesn't include any theme classes. This is > because the system doesn't appear to consider these as proper classes. > However, in trying to work out what themes can be provided and how to > derive from them it is essential information. For example, qx.theme.ext > doesn't appear in the tree, and qx.theme.Ext doesn't appear in qx.theme. > It all has to be found by searching the source code which makes > programming unnecessarily difficult. > > The documentation could just be a reformatting of the source code. > > Is this being considered? Should I raise an bug to cover it?
Not for the moment I would say. You can open an enhancement request however. APIs need some special view for the API viewer. But such a thing is not planned currently. The major question is what a theme in the API viewer would look like. What information should be presented there? A list of defined theme entries. The type of theme (widget, icon, appearance, ...) Please put all these things in the enhancement request using bugzilla. Thanks a lot. Sebastian > > Hugh > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
