My first qooxdoo trick is modifying the SplitButton example to have the
button reflect the selected value:
menuItem.addListener("execute", function(e){
button.setLabel(this.getLabel());
});
Where the anonymous function closes over the local variable button to
know who to set. As an exercise in learning qooxdoo, tho, I wanted to
find the split button instance by navigating up the qui hierarchy
looking for such a beast:
function getAscendantTyped(self,type) {
if (self) {
var par = self.getLayoutParent(); // not .parentNode it seems
console.log("getasc sees parents " + par);
if (par instanceof type) {
return par;
} else {
return getAscendantTyped(par, type);
}
}
}
This (or something close, I have been cleaning it up since pasting it
from my actual code) looks like it will work, but that "Layout" bit has
me nervous. Yet I cannot find anything more promising.
I got all excited about parentNode when I saw that used by getAncestors,
but then I could not find anywhere in the source that getAncestors was used.
So is getLayoutParent the way to navigate up a qooxdoo visual hierarchy?
kt
-------------------------------------------------------------------------
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
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
