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 -- View this message in context: http://qooxdoo.678.n2.nabble.com/Chrome-Plugins-tp5842811p5842811.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
