Hi Dietrich Yes, completely independent - it’s just a node app that is self contained; the code is written using Qx classes and the command line interface is a thin wrapper around them. I’m not intending to use grunt at all, I prefer that it’s focused on analysing code, generating dependency trees, and writing out the application in source/build/hybrid. So it’s a tool that your grunt script might execute to create the app, rather than being integrated into grunt.
I presume that it’s trivial to roll your own grunt task to execute something, and if you wanted to pass dependency information for grunt you could write a bit of code to pull it out easy enough. The database of dependencies etc is just in JSON. A command line interface is just a few lines of code - the API makes it easy to create all kinds of specialised tooling, e.g. Petr’s talked about creating custom builds of apps with all Qooxdoo classes, etc John On 23/12/2015, 10:21, "Dietrich Streifert" <dietrich.streif...@googlemail.com> wrote: >Hi John, > >is this completely independent from the latest grunt toolchain works in qx? > >http://manual.qooxdoo.org/devel/pages/tool/grunt.html > > >Am 23.12.2015 um 10:40 schrieb John Spackman: >> Well I’ve talked about it now so I’d better put it up! :) >> >> My plan is to get it finished off and release on github as an alpha before >> getting-paid work starts again on the 4th, I’ll post up here when it’s ready >> >> John >> >> >> >> > > >------------------------------------------------------------------------------ >_______________________________________________ >qooxdoo-devel mailing list >qooxdoo-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
