I've been using Qooxdoo very lightly for a few months, and I'm about to embark on a more involved development project. That leads to my question...
In the past few months, I've downloaded Qooxdoo from sourceforge.net using the zipped packages in the web browser view, starting with a released version back in March and followed by downloading the trunk version a couple of times since then in order to get some fixes in the trunk version. Each time I downloaded the zipped package, I extracted it into a new folder, saving the previous Qooxdoo download in a separate folder. I now have several versions of Qooxdoo in my local environment, but I always use the last one downloaded. In order to be able to have some sanity during aggressive development work, I'm wondering if I'm approaching my downloads of Qooxdoo incorrectly. If I need to modify my method of getting the latest Qooxdoo code into my ongoing development, now is the time to make the change to my method of downloading Qooxdoo. Note: I have not tried to use the "svn" commandline tool yet for this purpose, but I suspect it has the same pros and cons as my approach through the web browser. Are there any benefits to using svn versus downloading the zipped package through the sourceforge.net website? Can someone please comment on the best approach to setting up my local copy of Qooxdoo in a way that will allow me to easily update it to the latest trunk release without completely upsetting any ongoing development effort? In a related issue, my local RedHat environment has a system dependency on an older Python version, and I've had to edit critical Qooxdoo files with a custom Python version each time I've downloaded it in order to use the newer Python I installed specifically for Qooxdoo. Is there a way for the Qooxdoo toolchain to provide for a custom parameter for these Python references that will make this editing after download unnecessary. Specifically, at the start of critical Python scripts, I edit the "bang" entry to point to the non-system Python (#!/usr/bin/env python => #!/usr/bin/env python2.4), and several other places I have to change the Python command to my newer python as well (CMD_PYTHON = 'python' => CMD_PYTHON = 'python2.4'. It would sure be swell if Qooxdoo gave me a way to work around my multiple Python versions without any editing these files each time I retrieve the latest Qooxdoo version. TIA, Gene
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
