Hey, > this is probably a very simple question, but since I would like to do it > right, I thought it would better to simply ask: Why not, thats what the mailing list is for. ;)
> I have created a custom widget (which extends qx.ui.core.Widget). In the > widget I have only one child - a qx.ui.tree.Tree widget. > > I would like to expose the tree's contextmenu so that it will be possible to > set it from outside the custom widget. I realize I can define a contextmenu > property and bind it to the tree's contextmenu, but I can't help thinking > that perhaps there is a better way. Is there? Hm, it depends on what you want to expose. If its only one property, that's the most convenient way to do it. But make sure you copy the whole definition of the property in the tree because it might get confusing if your property allows null values e.g. and the original doesn't. > Another question, in this case when the custom widget has only one widget, > will it be better to extend directly qx.ui.tree.Tree rather than > qx.ui.core.Widget? That also depends on what you want to expose. If you want to "hide" some of the trees methods, this is the only way. If you plan or don't care about whats in, extending the tree is the right choice because that does not create an additional widget and with that another set of DOM elements in your app. I hope that helps, Martin ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
