This should be straightforward once the continuous compiler process is done – I
will implement that as an API too, so integrating with an HTTP server
implementation would be trivial and could be done as a separate contrib or PR.
I’ve been using https://www.npmjs.com/package/http-server and find it fast and
functional; a brief look at the code shows that it’s pretty lightweight
John
From: Dimitri <mi...@cargosoft.ru>
Reply-To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net>
Date: Monday, 22 February 2016 at 16:58
To: <qooxdoo-devel@lists.sourceforge.net>
Subject: Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and
100% Javascript API to building applications
Feature request: background recompiler + web server + reloader
In qooxdoo development, it's common practice to use a micro HTTP server to run
applications, eg. python -m SimpleHTTPServer, generate.py source-server,
editor/IDE embedded etc. This is because of limitations of file:/// addressing
scheme and CORS/XHR issues that it has.
QxCompiler is going to introduce another background process for live code
transpiling. Why not combining these two, so that the developer doesn't have to
launch two separate processes?
It should be pretty easy to serve static contents from Node. In the future,
automatic application reloading could be implemented, something that is
available now with generate.py watch + source-server-reload jobs.
Dimitri
------------------------------------------------------------------------------
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
