Cool :) I honestly never gave a thought to folks not having full control of their servers and stuff... And you are absolutely correct! qooxdoo has a lot of different ways to use it.. and that's why I hold them cards close! I have only three libraries I ever consider for UI (can't learn them all after all)... QooxDoo, My Own Dated Looking but lean-n-mean html/script lib/template system , and one other I won't name. QooxDoo is on harddrive speeddial!
Thanks for your comments thron7! --Jason thron7 wrote: > Jason, > > I fully acknowledge the ease of a programming model when just coding > against a library. But you have skillfully set up your web server to > provide the image stuff, which would be necessary even if you didn't > bother about an own theme at all, just because the qooxdoo widgets always > use a theme. > > Anybody with a similar environment could do the same, and enjoy a > "build-free" programming model. But not everybody is in this posiiton, > either because they don't have web server to work against, or wouldn't > know how to set things up successfully. And we couldn't help getting > server configurations right, debugging URL rewriting schemes and the like. > > If I were to write a qooxdoo app, maybe I would do it like you, or I would > use the 'source-all' job which has a similar effect for the source > version, or I would simply copy the setup from the Playground application > which also includes "all" qooxdoo classes... There are so many > approachable ways to achieve a build-free (or nearly build-free) > programming model with qooxdoo, but people have to find out for > themselves... > > T. > > >> 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 >> >> >> >> > > > > ------------------------------------------------------------------------------ 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
