dblacha wrote: > > thron7 wrote: > >> >>> right! >>> thank you for instruction: I was trying in that way, but without >>> ".firstChild" property. >>> but... is it that property in API document? >>> the qx.dom.Element is deprecated in 0.7.3 API and has not any property >>> called ".firstChild"... >>> >>> >> Widget.getElement() >> (http://demo.qooxdoo.org/current/apiviewer/#qx.ui.core.Widget~getElement) >> does *not* return a qx.dom.Element, but a *DOM node*. From there, you're >> in the realm of DOM APIs (see e.g. >> http://developer.mozilla.org/en/docs/DOM:element.firstChild). >> >> T. >> >> >> > > OK., that's now clear for me. I now understand, that all a not-linked-to, > function return type or a property in API, is just a DOM or a JS object. I >
Exactly. (I had to read that thrice, but now I got it :). Yes, to put it the other way round: In Apiviewer, type information like the return type of a method will be linked to the respective qooxdoo class, if it indeed *is* a qooxdoo class. Otherwise, the type is just a string representing a native JS type. - Yes, maybe not immediately obvious, more one of the subtleties of the Apiviewer (Are you all aware of the built-in search facility?!). T. > must be reading an API more carefully :) > thank you. > > db > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
