No problem; the next release will have a dbFilename property on 
qxcompiler.makers.Maker, so compile-app-demo.js now has this:
// Makers use an Analyser to figure out what the Target should write
var maker = new qxcompiler.makers.SimpleApp("qxt.Application", 
"qxt.theme.Theme").set({
  // Targets know how to output an application
  target: new qxcompiler.targets.SourceTarget("../testdata/qxt/source-output"),
  locales: [ "en", "es" ],
  dbFilename: "my-qxcompiler-db.json"
});
dbFilename is relative to the target output dir, or it can be absolute.

John

On 18/02/2016, 11:16, "Dimitri" <mi...@cargosoft.ru> wrote:

Feature request: shared cache
=============================

It's common practise in continuous integration that CI server does a
clean checkout per each build. Incremental builds are common practise
too, but they can be unreliable and problematic, especially for complex
builds.

At the moment, QxCompiler maintains a per-project cache that is
populated on first compilation. This might take significant time (up to
1 minute; subsequent builds are incredibly fast though). Original
qooxdoo generator solves this by using platform-wide cache, usually in
$TMPDIR/qx{version}/cache. This also speeds up compilation if there are
several projects using the same qooxdoo version.

It would be nice if QxCompiler supported shared cache in the same
manner. Please mind that configurable cache path is important.
Hardcoded $TMPDIR/smth works bad, because on modern Linux distros
$TMPDIR lives in ramdisk and is cleared at each boot.

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

Reply via email to