Hi Fritz, obviously, the local file system setup of a qooxdoo user cannot be hard-wired into the projects of qooxdoo-contrib. Therefore each contribution has a "generic" way of addressing certain qooxdoo versions (either SDK or SVN). See the following documentation at http://qooxdoo.org/contrib/join#contribution_skeleton "Setup file system links from the qooxdoo folder within the qooxdoo-contrib checkout to your local copy of the qooxdoo framework. Please see the README.txt file in the qooxdoo folder just mentioned."
So each user can and needs to setup links to his/her specific qooxdoo versions. This uniform concept of linking to all the various qooxdoo versions, will allow for (semi-)automatic maintenance of the contributions in the future (e.g. generating demo builds, etc.). Referencing contributions (e.g. from a demo to the corresponding contribution itself) is done by relative paths (e.g. ../../). This would also work for referencing another contribution, at least if you've checked out the entire trunk of qooxdoo-contrib. Alternatively you could use the "contrib://" pseudo protocol so that it gets downloaded automatically. HTH. If you've got questions, please get in touch with me, Andreas PS: The demo configs of SmartTableModel did look ok, but I'll try to confirm that they work as intended. On Sun, 2009-10-04 at 20:52 +0200, Fritz Zaucker wrote: > Hi, > > I am a bit unsure about the "proper" directory layout of a Qooxdoo checkout > together with qooxdoo-contrib (and thus the right settings of QOOXDOO_PATH > in config.json). I assume: > > - for SDK > > cd someplace > svn co https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo qooxdoo > svn co https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib > qooxdoo-contrib > > as documented on > http://qooxdoo.org/documentation/general/checking_out_from_svn > > The only "undocumented" part is, if qooxdoo and qooxdoo-contrib should be > at the same directory level. This is relevant, when setting QOOXDOO_PATH > in the config.json file of a contribution. > > If the above description is correct, then I guess the QOOXDOO_PATH > settings in the contribution SmartTableModel are incorrect. > > - for trunk > > cd someplace > svn co https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo/trunk/qooxdoo > qooxdoo > svn co > https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib > qooxdoo-contrib > > (in analogy to SDK above) > > I guess that leaves the question, what to do if using the SDK AND wanting to > use a contrib sitting in svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/ > > (like SmartTableModel). > > I guess I can EITHER use svnroot/qooxdoo-contrib OR > svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/ > > Cheers, > Fritz > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
