Hi Dimitri
Thanks for the kind words :) The delay in releasing has been finding the time
to do some proper testing before opening it up to scrutiny, but I've got it
running the whole demo browser from Qooxdoo now and that's a pretty varied set
of tests. The documentation isn't exactly extensive (yet ;) ) but there are
some demos and I'm around on this ML or Skype to help out. I think that it can
do what you need :)
Regards
John
----------------------------------------
From: "Dimitri" <mi...@cargosoft.ru>
Sent: Friday, February 12, 2016 12:06 AM
To: qooxdoo-devel@lists.sourceforge.net
Subject: Re: [qooxdoo-devel] How to make parts independent
John, Thank you for you efforts, and please be sure you've got another beta-
tester and probably contributor(s). Some background first. We are developing a
massive qooxdoo Desktop application. When we were about to roll integration
tests, it turned out that our app doesn't run in PhantomJS - because of
Promises that we heavily use in our app. Up to this moment, supporting legacy
browsers was not our primary objective, but certainly that PhantomJS issue was
something to be dealt with. Lack of Promises is a well-known problem in
PhantomJS [1]. The guys have already begun transitioning to CEF [2], and it's
unlikely that PhantomJS gets Promises until then. God knows how long will it
take, considering another ~1500 open issues. From the discussion [1] I've
learned about Babel. Employing Babel would not only solve the PhantomJS+Promise
issue, but would also allow us to use full ES6, at the same time making our app
compatible with legacy browsers. I've started to investigate how to integrate
Babel into qooxdoo toolchain, but suddenly stumbled upon this thread. Needless
to say how excited I was :) I wish you luck, and kindly ask you please to keep
us informed. P.S. Thanks for the excellent UploadMgr, we've been using it in
our project since the very beginning. It has been a real time saver for our
developers. [1] https://github.com/ariya/phantomjs/issues/12401 [2]
https://github.com/ariya/phantomjs/issues/10209 > 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
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance APM +
Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end
web transactions and take corrective actions now Troubleshoot faster and
improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________ qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
