I'm definitely a sympathizer for big complete qooxdoo bundles. As for themes.. I'm using themes in my web server and it basically relies on a simple directory structure arrangement with like named gfx files in each "theme folder" and same file names dir's etc...
/xfiles/web/img/gfx/theme1/sometree /xfiles/web/img/gfx/theme2/sometree Then I have one variable with: /xfiles/web/img/gfx/ Another with the current theme: theme1/ Then all the gfx use: var1 + var2 + /sometree/somefile.png or whatever. I find it's so easy to dig in when you download the big library - and just start invoking functions and classes without trying to get the build environment working which I have to say has been a nasty beast even when I got it working I didn't get a good feeling about how things had to be arranged. Using (older and some after-market qooxdoo bundles) I found it was easier for me in that I could work on the application and not fuss about. And frankly.. I didn't worry about themes all that much... and I still got pretty "unique" results. My two cents. --Jason P Sage ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
