You might consider creating bugs for API docs that you feel aren't intuitive, and suggest wording that you think would be clearer.
Derrell On 2010-03-06, Stefan Meyer <[email protected]> wrote: > The description often very short and when i read something like it > give back the elements and i get the elemnts numbers, thats very > confusing. when i read that i get back the object, i think i gt a > reference to the object. Often their missing only a little example > or when i see a method , their often no possible options listed. > > thats all everything other than intuitive. > > on the other hand , i miss a good editor with codecompletion. >> Hi, >> >> answer is in the API documentation: >> >> http://demo.qooxdoo.org/1.0.x/apiviewer/#qx.ui.core.Widget~setEnabled >> >> Qooxdoo API is very intuitive, I'd like to see the reason why you >> didn't find the answer there, where you looked before? >> >> Thanks >> >> > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- Sent from my mobile device ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
