Re: [qooxdoo-devel] Build optimization issue

2015-01-27 Thread halcwb
Thanks, I am sure it is in the manual, but TL;DR. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Build-optimization-issue-tp7586691p7586738.html Sent from the qooxdoo mailing list archive at Nabble.com. ---

Re: [qooxdoo-devel] Build optimization issue

2015-01-27 Thread John Spackman
You need to surround the code with a check for the debug version: if (qx.core.Environment.get(“qx.debug”)) { this.assertX(); } The generator will completely remove debug code inside this kind of test. If you want to keep the assert at runtime, use qx.core.Assert.assertXxxx directly John

Re: [qooxdoo-devel] Build optimization issue

2015-01-27 Thread halcwb
I still have the problem, for example the below code works well in the source version but fails in the build version, because the assert methods are not recognized by the compiler to be included. qx.Class.define("genpres.Application", { extend: qx.application.Standalone, implement: [genpres.li

[qooxdoo-devel] Build optimization issue

2015-01-16 Thread halcwb
I have a situation in which I call a method of a subclass in a superclass. This is a native qx method, but the build version only adds methods to the subclass it assumes to be used. So now I have implemented this trick: ###* @ignore(_.*) ### qx.Class.define "informedica.controller.BaseController