Hello, I'm a bit confused about your solutions: "either wrap the google code in your popup window inside a small qooxdoo app or use a qooxdoo window instance and embed the google code there inside an iframe"
If I was to load a qooxdoo window and embed the google code there, then I would have no way to position the popup window at a marker's position on the google map precisely, which doesn't really solve this problem. If I was to wrap google code in the popup window inside a small qooxdoo app, then 1) Would I need to create a separate qooxdoo app for each popup window that I make? 2) How would separate qooxdoo app communicate with my "main" qooxdoo app? 3) Not exactly sure how to achieve this on an implementation level...?? Is there other way around this problem? Maybe I am a bit confused but... can I supply some qooxdoo / javascript code in a HTML string and use that code to talk to my "main" qooxdoo app? Thanks! mckwil Alexander Steitz wrote: > > Hi, > > On Thursday March 4 2010 17:22:18 mckwil wrote: >> I'm trying to build an application that integrates with Google map, in >> which I need to create a map marker with a pop-up information "window". >> >> What I wanted to achieve, is to use Qooxdoo widgets/components in that >> pop-up to generate richer looks/behaviour. However, according to google >> map's api, I can supply either a content Node or html String to construct >> this pop-up window. >> >> Is there anyway I can nicely wrap Qooxdoo components (along with their >> behavior) in a Node object to pass to google's info window? >> >> I know each widget has two methods getContentElement() and >> getContainerElement() to return qooxdoo's element object. Which one >> should >> I use? And should I call getDOMElement() on the return value to extract >> the actual DOM node? or is there some other way for doing this correctly? > The "containerElement" is the outermost element of a qooxdoo widget and > the > "contentElement" is its direct child. With the "getDomElement" method you > can > retrieve the actual DOM element which is used (that implies that the > widget is > already rendered/visible). > > However, even if you access the DOM element of a widget and you pass it to > your google popup window this won't solve your issue, because you only > have > passed the pure DOM elements. You have to ensure that a qooxdoo is running > inside the popup window because the behaviour of qooxdoo widgets rely on > some > core classes. > > So I guess the only way to get around is to either wrap the google code in > your popup window inside a small qooxdoo app or use a qooxdoo window > instance > and embed the google code there inside an iframe. > > 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 > > -- View this message in context: http://old.nabble.com/Get-a-node-to-represent-qooxdoo-widgets-tp27783016p27795424.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
