Hi the list, 0.8.3 is out and I decided it could be a good time to give the qooxdoo python build a chance.
Unfortunatly, I'm not able to make it work in my environement after hours of work. On the command line + vi, it works fine and I think I now understand the difference between generate source and generate build. In the config.json, the QOOXDODO_PATH had to be set. This, as far as I understand, set both the build-time path from generate.py to the SDK and also at the samz time the run-time path to the SDK under the web server. This doesn't matter for generate build because qx classes are embeded but this make for me the generate source to fail (or source-all, not sure about the differences). In fact, in my case, the SDK do not have the same path at build-tima and at run-time. I also see that the generate.py is a kind of proxy to generator.py, is there a way I could move the SDK by removing the need os using config.json QOOXDOO_PATH variable look like to have to usage ? By doing that, I hope I'll be able to set the path only to the run- time place of the SDK ... Any advice or other ideas more than welcome :-) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
