Hello to all. I don't want to start a flameware, but I have some ideas and I want to know what to you think about it.
To create a new application you need to do: $ /path/to/qooxdoo/tool/bin/create-application.py --name myApplication It creates the application struct: ./config.json ./Manifest.json ./source/* ./readme.txt ./generate.py To build the application ./generate.py build I think center all qooxdoo funcionalities into only a program is a better approach. Something liks this: $ /path/to/qooxdoo create-applicaton --name myApplication And to build: $ /path/to/qooxdoo build # or maybe job=transform,build,etc This eliminated the file ./generate.py and keep in the project directory only the project code. If the user put qooxdoo into the PATH env var, it can just call... $ qooxdoo build .. to build the application Currenty if the user change the qooxdoo framework location, it needs to adapt the config.json file. In my opinion the most dificult part in qooxdoo is the setup :-) With this approach the user just needs change some env variables, or optionally change it in the let session in config.json. In adition news commands could be implemented in the qooxdoo application. For example: $ qooxdoo create-class myApplication.admin.BlackList [--extend qx.ui.form.Button] [--type singleton|static|etc] And the class skel would be placed in the correct directory. I don't have skills to do it, so I can only sugest it ;-) Regards. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
