I think you can/should run the migration job directly in the "old" setup (no
need to create a new 3.0 application and copying stuff over).
But Thomas will probably elaborate ...
Cheers,
Fritz
On Thu, 15 Aug 2013, Stef wrote:
> 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
--
Oetiker+Partner AG tel: +41 62 775 9903 (direct)
Fritz Zaucker +41 62 775 9900 (switch board)
Aarweg 15 +41 79 675 0630 (mobile)
CH-4600 Olten fax: +41 62 775 9905
Schweiz web: www.oetiker.ch
------------------------------------------------------------------------------
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
