Thomas, that’s interesting about the grunt development in next, I had no idea it had gone so far.
Stefan, I’ve been thinking about not reinventing the wheel, esp. in light of Thomas’ comments, and my thought is that QxCompiler should be able to produce an application from source, from the command line and the use of Grunt (or Gulp, or brocolli, etc) should only be required for more advanced, custom tasks. My rationale for this is that QxCompiler only needs a simple command line in order to achieve this (for new and experienced users), and does not require any kind of third-party build tool with all the learning that is required to get started with one. One thing I would recommend is to look at dropping the config.json support altogether (and Python); with the compiler functionality being replaced by QxCompiler, most of what’s left is definitely in the area of grunt/gulp/etc; eg generating API docs, generating complete demo apps, distribution kits, etc. Although I can have a look at Grunt, I have no experience with it and my focus is on QxCompiler at the moment; briefly looking through the next master/tool/grunt repo, the source looks interesting but will probably take some time to get to grips with Grunt to really use. Is this something you could help with? Like QxCompiler, it could be developed as a separate contrib and I’d be happy to help with parts of the QxCompiler API to support you. Regards John On 22/02/2016, 21:10, "d...@cost-savers.net" <d...@cost-savers.net> wrote: >Thomas, > >> I could see Grunt being a command-line frontend for the jobs, with >> QxCompiler remaining a pure API-based library which is included as a >> dependency and utilized from Grunt files. > >I agree completely with you in this! Don't invent the wheel again! > >> Even if you feel the code in qooxdoo.next is too 'Grunt-heavy', or would >> just like to hack on an all-new, own version of Grunt support (which I can >> always understand ;-)), the code in qooxdoo.next might be a good >> inspiration to draw from. > >No new hack. Reuse what already exists because it is good for what it was >done. I have looked at it. It can be used here. > >Stefan > >> T. > > >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > > >> _______________________________________________ >> qooxdoo-devel mailing list >> qooxdoo-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > >------------------------------------------------------------------------------ >Site24x7 APM Insight: Get Deep Visibility into Application Performance >APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >Monitor end-to-end web transactions and take corrective actions now >Troubleshoot faster and improve end-user experience. Signup Now! >http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >_______________________________________________ >qooxdoo-devel mailing list >qooxdoo-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
