You probably can’t integrate the Qx class system with ES6 class system (not without a lot of framework changes anyway) but you can use ES6 with Qx, there’s lots more to ES6 than just classes and Qx classes have some really useful features that ES6 does not have, eg properties and events.
I don’t see how you’re going to get away from Javascript by using PythonJS – all the core source code and all the contribs and all the docs will be in JS. But good luck with it, let us know how you get on :) From: Phyo Arkar Reply-To: qooxdoo Development Date: Friday, 11 September 2015 10:58 To: qooxdoo Development Subject: Re: [qooxdoo-devel] How hard it is to integrate Coffeescript on Qooxdoo? If someone can integrate Coffeescript in qooxdoo , PythonJS will be fine too. But PythonJS is just very new kid , nobody know it yet. PythonJS transpiler from Rusthon by Harts Antler , is 100% compatible with JS , just like Coffeescript . https://github.com/rusthon/Rusthon ES6 classes aren't compatible with qooxdoo class system. So we have to ditch qooxdoo if we want to use ES6 right? And , frankly , i do not like javascript at all. I Tried to love it for 14 years , but i just can't lol :D , even tho Qxdoo made javascript much much better. I just can't wait WebAssembly , and other langauges porting to compile webasm. On Fri, Sep 11, 2015 at 3:51 PM, John Spackman <john-li...@zenesis.com> wrote: Hi Phyo Your subject said CoffeeScript but the message said PythonJS? I presume you meant just one or the other? In theory using a transpiler like CS should be fine (someone here has already had success with Typescript), but perhaps that’s partly because CS (as I understand it, I’ve not used it myself) is designed to map pretty clearly into JS; converting from Python into JS, I’d be concerned that something would be lost in the translation and you might find yourself unable to integrate certain things or having to resort to low level hacks to get stuff working. On a practical level debugging your app could be a problem unless there are suitable source mappings (that work) and there’s presumably duplication between runtimes. On top of that, to try and get PythonJS’s object model (which may be internal/undocumented and subject to change?) integrating with Qx would presumably need modifications to PythonJS’s transpiler and runtime – a potentially major undertaking. How about using Babel to be able to code your app in ES6? Then everything is pure Javascript (yay!) and you can code to the future standards of the web. John From: Phyo Arkar Reply-To: qooxdoo Development Date: Friday, 11 September 2015 09:38 To: qooxdoo-devel Subject: Re: [qooxdoo-devel] How hard it is to integrate Coffeescript on Qooxdoo? Should i go Qx-Typed way of doing ? it uses compiled qooxdoo inside typed script. On Fri, Sep 11, 2015 at 1:16 AM, Phyo Arkar <phyo.arkarl...@gmail.com> wrote: Has anyone tried? Any success story? Coz i am going to use PythonJS inside qooxdoo if it is possible. I can't find a way to integrate , yet , unless compiled. If we can map PythonJS's OO with QxOO , it can work? ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
