I am having a hard time using qooxdoo like a library. For some reason it is difficult for me precisely describe my problem. I just find myself fighting with makefiles, skeletons, quickstarts without getting anywhere.
When I use the skeleton I end up with a source and a build version of the javascript code. This is not bad per se. But I also have a python RPC backend. The python application code I write would also have to come in two versions (source/build), which is not that easy and does not provide much benefits (except concealing the source) The qooxdoo *build* code no longer separates library code from application code. It looks like an application with a statically linked library and is thus self-contained. I have a hard time doing the same with my python application code, i.e. I can compile python code to pyc files, but creating a self contained thing is much harder. My preferred way of using qooxdoo with a python backend would be: qooxdoo acts like a library and so does the python rpc code. No matter how I set this up and build or compile things, I will do this only once. The application consists of a javascript part and a python part. The javascript part uses qooxdoo as a library and the python part uses the python rpc library. I may want to compile my application as well, but this is not essential. I was hoping that the quickstart would do just that, but I am getting errors like Could not preload: widget/splitpane/knob-horizontal.png, widget/splitpane/knob-vertical.png ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
