Hi. Build & deploy model: when needing to debug on a server, this is tiresome, to say the least. However, we found a way around it, which makes a rebuild necessary only when you add classes: you copy qooxdoo-1.1-sdk/framework to the server, in a path similar to the relative path where you have it when you develop locally - the ugly thing being that you need to place the qooxdoo sdk inside your source directory on the local machine for this to work.
However, we also discovered that with any browser, reloading the app in the browser takes ages, so I think I now know why the qooxdoo developers chose to include a build mechanism - if you get load times of a minute right from the start, you might get thrown off way before you get hooked. Alternatives to qooxdoo: I'd surely go for something nicer than qooxdoo. However, looking at the alternatives, IMO nothing comes even close to qooxdoo. There's ext, which is a nono due to its licensing model and memory leaks in IE, there's YUI, which is still a lot more buggier than qooxdoo, there are many other frameworks, which are even less mature than qooxdoo. Another strong selling point for qooxdoo, IMO, is the fact that you don't have to touch HTML an CSS. The moment you have to work with HTML and CSS, your browser independence has vanished. I think many people on this list know what it means to have to test your app on five different browsers, then use various quirks to get around browser differences. You don't get this with any other framework, or at least not with any that I know of (well, sort of, I just had a look at cappuccino.org, but technically it's ages behind qooxdoo - a lot less well structured, and less well supported, IMO - which btw is another strong selling point for qooxdoo). Big qooxdoo users: 1&1 isn't that well known outside Germany, GMX even more so. 1&1's visibility is somewhat limitted to professionals. IBM or RAP, on the other hand, are quite visible around the world, and IBM rings a bell with execs too, not just with IT professionals. I (and a few others too) told you qooxdoo has a problem with marketing, seemingly it's still a surprise for you. Problem integrating contribs: It's not that obvious that you're considering contribs something like an incubator. OTOH, as long as there's no way that contrib authors can work on the core framework code, should you decide to integrate contribs, it's pretty obvious why you don't get to do more work in qooxdoo. IMO, a mechanism where ppl contribute and you just supervise integration is required in order for qooxdoo to really take off. Right now, it's difficult to contribute to the core framework for outsiders, IMO. I'm sure 1&1 has excellent project managers and marketers in-house. Why don't you ask for some help from them? IMO, a development model where external contributors can contribute easier and better marketing would help both external users of qooxdoo and internal 1&1 users. 1&1 as a company would also benefit from a larger community, gaining better visibility outside its somewhat narrow geographical and technological business area. The core qooxdoo team is built of programmers, who may have the brains but surely don't have the time to set up such a model, or to organize marketing. But there might be other people willing to help, if they're asked. br, flj ------------------------------------------------------------------------------ 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
