This is also the answer to your question in different topic, I hope it's not a mess :)
On Mon, Jun 14, 2010 at 11:03 PM, thron7 <[email protected]> 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. I think that this is not problem. If anybody is experienced to setup web-server then there shouldn't be problem to understand that you need to copy some files into the public or private directory that is served. > 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. I do not understand here, how is possible to develop web application without a web-server? Of course you can write some GUI using file-system, but the rules are the same for web-server, just copy needed files & run, this is how it works. I think that URL rewriting and such things are really not needed to deploy or work on an application. I coded using Python, PHP and Java and I don't see the problem here, really. > 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... Okay, this is possibility, but we are still at the compile time problem. What if I need to include widget that has some own theming at run-time? What about easy creation of contribs (copy & run), etc? Maybe this is problem. Of course user can choose QxBuild, but it's just generator example how to build qooxdoo to one file, if you need for example upload widget or html-area then you need to understand how generator works and you need to generate your own qooxdoo all-in-one. Because all icons, assets, etc must be known (correct me if I'm wrong here). Personally I like the idea of packages. It works, many users are comfortable with it and today there is not difference between 1000kB js file or 1200kB js file. And also packaging qooxdoo to smaller pieces also means that some browsers (firefox for example) will not hung when reading such big .js file. Just my notes. I really like to help with that. If you have questions it's no problem for me to help, to write ideas how such packages should work, to think for you:) I think that we can take advantage of javascript dynamic nature and trying to scumble it (compiler, resources, static everything) is not good move. But of course using generator to build qooxdoo packages is good thing. -- Best regards - Petr Kobalicek <http://kobalicek.com> > 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 > ------------------------------------------------------------------------------ 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
