T. Thanks, that is certainly a good start for the GUI side of my extension, in this case the popup box when I click on the "browser action". The reason I ask specifically about a separate skeleton for the work is that an extension can have two primary HTML pages - one that runs in the foreground when summoned by the user and would house the GUI and another that operates in the background continuously within a full WebKit frame with window and DOM but which is never displayed to the user.
I haven't seen any of the current tutorial or demo apps yet which focus on this multi page approach, since Qooxdoo seems to operate under the presumption that the whole app loads off of one page. I presume it is as easy as creating a background.html parallel with the provided index.html and that with all of its scripts will be translated directly to the build directory when I run generate.py the same way index.html is? --Greg On Thu, Dec 16, 2010 at 12:24 PM, thron7 <[email protected]> wrote: > Greg, > > welcome! > > Daniel has tinkered with Chrome extensions (we believe this is what you > mean). The base line is that you can use a stock qooxdoo 'gui' skeleton > to start off. You need to add a Chrome manifest file by hand, though. > Otherwise, you just edit the skeleton to your heart's content, then run > 'generate.py build', and open the ensuing 'build' subdirectory in > Chrome's developer mode. That should be it! Make modifications in the > 'source' tree and cycle. > > Let us know how you fare. > > T. > > On 12/16/2010 06:49 PM, greg.hellings wrote: >> >> Greetings, >> >> I have stumbled across Qooxdoo while looking for an alternative to ExtJS >> because of its unfriendly licensing model but excellent widgets and >> object-oriented JavaScript-driven application model. Among more traditional >> web uses, I am also developing a plugin for Google Chrome. Currently with >> ExtJS I can simply include their library inside of the Chrome Extension >> directory while developing and summon the files I want out of the HTML files >> which comprise the pages of my plugin (for those of you who may not know, >> all Chrome plugins are composed entirely as HTML/JS webpages and supporting >> image and CSS files). >> >> I was curious if anyone here has experience using Qooxdoo as their framework >> inside of a Chrome extension and if there is a current application skeleton >> which I could base a plugin off rather than rolling a standard Qooxdoo >> application and then manually copying and installing that to my Chrome >> extension's development directory. Adding that extra step would make >> development iterations more cumbersome rather than less. If not, I'll try >> fumbling with the application skeletons myself, but I didn't want to >> duplicate work if there is already such a skeleton lying in someone's >> closet. >> >> --Greg > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
