Hi Dimitri
Thanks for checking out so quickly :)
Re: npm and docs: done
Re: qooxdoo submodule and https: fixed
Re: QOOXDOO_PATH: no - that's a generator.py/config.json setting and
config.json files are completely ignored; when using the QxCompiler API, once
you have told it where the Qooxdoo library is you have done the equivalent of
setting QOOXDOO_PATH. Of course, as it's API based you can define variables
etc as suits you best :)
In test/compile-app-demo.js it adds the Qooxdoo library like this:
maker.addLibrary("../qooxdoo/framework", cb);
Just change the path to point to your preferred location for qooxdoo. To make
this a bit clearer, I've just modified the test/compile-app-demo.js to declare
a variable QOOXDOO_PATH
I expect that the command line version will imply have a search path for
libraries and just auto-discover by searching for Manifest.json files.
Re: missing testdata/qxt: something went wrong with your checkout, that
directory is definitely there.
Re: build (and source-hybrid) targets: to control output for Source vs Build
vs Source-Hybrid, the API classes qxcompiler.targets.SourceTarget,
qxcompiler.targets.BuildTarget, and qxcompiler.targets.SourceHybridTarget are
used; test/compile-app-demo.js uses the SourceTarget but you should be able to
switch it easily enough. I say "should" because I realise now that I havn't
tested them for a few weeks now and I should give them the once over ASAP :)
I've got to go out shortly so I'll take a look this evening.
John
----------------------------------------
From: "Dimitri" <mi...@cargosoft.ru>
Sent: Sunday, February 14, 2016 2:27 AM
To: "qooxdoo Development" <qooxdoo-devel@lists.sourceforge.net>
Subject: Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100%
Javascript API to building applications
John, congratulations with the long awaited release! :) qooxdoo guys, do you
think that project like this could at some moment land in qooxdoo and get
official support? What about qooxdoo patches (mostly strict mode compatibility
related, AFAIK) - could they be merged upstream? This would reduce maintainship
costs for those who want to experiment with both QxCompiler and official
toolchain. I didn't yet try QxCompiler with my project - I feel I yet lack some
understanding of how it works. However, I tried to test it with the skeleton
app. Off the top of my head: - one needs to do "npm install" first and to run
test scripts with "node <script>.js". This might be quite obvious for those
experienced with Node, but I guess the docs will nevertheless benefit from
mentioning this; - it's not easy to clone a repo unless you've set up Github
SSH access. This is because of "qooxdoo" submodule pointing to
"g...@github.com:john spackman/qooxdoo.git". Could it be a HTTPS URL instead? -
does QxCompiler honour QOOXDOO_PATH setting? How do I define qooxdoo location
if it is different from the bundled one? - testdata/qxt directory doesn't
contain skeleton app. In order to play with test scripts, one needs to create
the app manually (as "skeleton.Application"?) and copy it to the said location;
- does lib/compiler.jar really belong there? Most importantly, I was unable to
find clear instructions how to produce a single-script minified build (a-la
"generate.py build"). By deafult, QxCompiler produces a bunch of JS files,
which significantly slows down loading and, obviously, is not acceptable for
production. Is it possible at all with the current version (maybe in
combination with classic generator)? I hope these are just minor issues. After
all, you've done a great job :) I wish you good luck and further progress wih
QxCompiler. Dimitri > Hi all > > There is a first release of my QxCompiler that
adds ES6 to Qooxdoo > applications and replaces the generate.py toolchain with
a faster, > 100% Javascript tool that is easily extensible. > > You can find
the first release at GitHub here: https://github.com/joh > nspackman/qxcompiler
> > It's an alpha release, but something that's been in development for a >
while now and which I'm starting to build into my production > servers. > >
I'm very open to pull requests or collaboration, and keen to see this > become
a useful tool for myself as well as others so any questions > etc please ask. >
> Regards > John > > > > > >
------------------------------------------------------------------- >
----------- > 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
