Hi, as the demo browser for contributions is being finalized, I wonder about one thing in the demo Manifest files. When I build the contribDemoBrowser now, it will complain about non-existent qooxdoo versions and skip the demos that are flagged to work with these versions, such as, for example "1.0", because there is no "1.0" symlink in the qooxdoo/ folder of my local qooxdoo-contrib working copy. However, it does not complain about "1.2pre" which does not exist, either (although "trunk" does exist). Does that mean we're supposed to use "1.2pre" rather than "trunk" in the Manifest files and it will automatically figure out that this is a trunk version (and complain if the trunk version has changed?). That would make sense and would be much smarter than "trunk" since the trunk is a moving target.
Just let us know so we can update the Manifest files accordingly. I am looking forward to the contribDemoBrowser be published and I hope this will motivate people to update their qooxdoo-contrib projects and publish/update demos for them! Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/Manifest-files-for-contrib-demos-tp5358139p5358139.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
