Hi, thanks for the info.
Topic is not that important. There's no todo left.
For completeness or reference, just a remark on migration from 2.1.1 to 3.0:
thron7-2 wrote
> [...] But you should have received numerous messages about this
> during migration and running the source version of your app under 2.1,
> no?! The migration would also automatically have re-written your code to
> use the instance methods, so you should be fine with existing code.
The demo code of Application.js was:
...
var s1 = " demo-string ";
var s2 = qx.lang.String.trim(s1);
alert("/" + s2 + "/");
...
In the 2.1.1 version, no compile error, no lint warning, no runtime error.
When creating a new 3.0 skeleton, copying the previous Application.js into
the project and then running "generate.py migration", there's neiter warning
about trim(), nor automatic code update. Of course, a warning is dropped for
the replaced "asset" syntax.
Also "generate.py source" and "generate.py lint" doesn't recognize any error
or warning. But at runtime the browser throws the error "TypeError:
qx.lang.String.trim is not a function"
Anyhow ;) maybe I did the migration wrong way (as I've read in other posts,
it's a common thing)
Best regards,
Stefan
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/qx-lang-String-trim-method-removed-in-3-0-tp7584351p7584370.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
