Hi Peter, On Wednesday March 10 2010 14:12:54 Peter Schneider wrote: > we still have mayor problems with gmane (don't know if it's on our side...) > so sorry about my late reply. No problem at all.
> I've tried your suggestions and I'm getting closer :-D > Although there are still some mysteries to solve for me. > > Here's one for example: > When my class is derived from "qx.ui.embed.Html", the inserted HTML does > contain much more than I'd expected...(see attachment) > I wonder where those <a> elements came from. I will try to derive my class > from "qx.ui.core.Widget" like "qx.ui.embed.Html" does, so my class will > become a 'look-alike'. If you modeled the class like "qx.ui.embed.Html" then the "a" element can only end up in the DOM by adding it :) I mean: there is no magic code to insert an "a" element in the framework. It would be interesting how your class look like. > I mean they are both derived from the same parent class. Maybe that was > meant > > by you when you wrote: > > [...] You can use the class "qx.ui.embed.Html" as your base class and > > customize it. [...] I meant you can extend "qx.ui.embed.Html" and customize the "_applyHtml" method and the constructor. Extending "qx.ui.core.Widget" and adding your functionality like "qx.ui.embed.Html" class is also a possibility. > > Is is really important where in the DOM the nodes are added? > It's not really important; they are just easier to find that way ;) Nice :) cheers, Alex ------------------------------------------------------------------------------ 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
