Thanks Derrell :) I’ve been working on it on and off for ages, and adding babel put it back a bit but was such cool idea I couldn’t resist :)
John From: Derrell Lipman <derrell.lip...@unwireduniverse.com> Reply-To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net> Date: Wednesday, 23 December 2015 at 02:58 To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net> Subject: Re: [qooxdoo-devel] How to make parts independent John, that sounds incredibly cool! Derrell On Tue, Dec 22, 2015, 8:06 PM John Spackman <john-li...@zenesis.com> wrote: Hi Defero To make that work you’d need to be able to analyse the dependencies of each plugin on demand, and then load those classes to the client; I dont think you can do this with the current generator but as it happens I think I’ll have something that will do the job in the next week or so. I’m getting ready to release a replacement for the generator, written in 100% javascript and running under node.js; it’s API based and exposes dependency information, and you’d be able to use the API to incrementally scan dependencies of new classes (e.g. Add plugins on the fly and analyse them). It also supplies ES6 (via babel) and is way faster that the python version. The only potential snag is that while all the dependency detection etc is all working, there is not support for parts yet - you’d have to implement your own code to parcel up each part (or plugin) and load it on the fly, but because it’s API based that should not be a problem. It’s my holiday project to finish it off, and while it’ll be an alpha release it’s there and working apart from some translation work that needs to be done to finalise the ES6 implementation. So if you can hold off a week or so there might be something to look at :) Regards John On 22/12/2015, 14:08, "Defero" <krosela...@gmail.com> wrote: >Hi, > >it might work, but i think it's quite a dangerous hack. It's hard to find >any data of how the compiler works, is there any extensive documentations on >that? > >Does anyone have any ideas in general, how would you guy handle 1000 plugins >for example. (These are loaded only per user specific requests). >And if we want to allow full access to qooxdoo functionality with it, i >can't see a good way of achieving this. >Either you have 1000 libraries and you include them in the build, or you go >with the un-optimized build-all approach. > >I hope i'm missing something. > >Regards, >Defero > > > >-- >View this message in context: >http://qooxdoo.678.n2.nabble.com/How-to-make-parts-independent-tp7587856p7587863.html >Sent from the qooxdoo mailing list archive at Nabble.com. > >------------------------------------------------------------------------------ >_______________________________________________ >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
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
