Hi Christian! > I am currently finishing a Wizard Widget for the qcl.ui.dialog package and > once I am finished, I would like to create a page for the demo browser > demonstrating all the dialog widgets (alert, confirm, select, form, login, > wizard). However, I don't know how to go about doing this - how do you > create a demobrowser page that has dependencies to a qooxdoo-contrib > project?
You'd suggest you start to create individual demos that run stand-alone. When using the contribution skeleton with create-application.py (all in the trunk), a pre-configured project structure is being established. See http://qooxdoo.org/contrib/join#contribution_skeleton You may want to create such a test contribution locally to figure out and copy the setup over to your actual qcl contribution. Newer contributions would benefit from using the new setup right from the start. Next to your actual contribution code you'll find a demo/ folder that holds all the individual demos. Such a demo is a complete regular gui skeleton, so you have all the possibilities to describe it (Manifest.json) and configure it (config.json). The regular generate.py targets source and build should work. In order to auto-generate the demos, a common reference to the qooxdoo releases (or trunk) is needed. This is made possible by creating such uniform references in form of symbolic links within the qooxdoo/ folder of qooxdoo-contrib. The README.txt in this folder explains how to do this for all OSes. The built demos - being self-contained - can easily be put online. That's how the HtmlArea demos were created, e.g. http://demo.qooxdoo.org/contrib/HtmlArea/trunk/demo/native/index.html Of course, there is still a way to go to merge the framework demobrowser and the demos of qooxdoo-contrib. In the long run they should end up being backed up by pretty much the system, i.e. for each library (like qooxdoo-contrib) and the framework itself it should easily be possible to create a corresponding demobrowser (that of course may reference or more tightly integrate each other). There are a few proposals around, and we're in the progress to decide on the direction to follow and the next milestones. For a start, we'd need to unify the existing (newest) contribs anyway. So I'd like to help you with pushing the qcl demos and smoothening any rough edges. We're both at the same time zone ;-), so lets get connected tomorrow, if you like (ICQ), and do the adjustments while being in touch. TTYL, Andreas -- Andreas Ecker Project Lead http://qooxdoo.org ------------------------------------------------------------------------------ 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 qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
