Hi Defero
Sorry for the delay in getting back to you, it's been a very busy week
I've not used parts in Qooxdoo, but AIUI you associate classes with a
named part, and then use the API at runtime to force the loading of the
part; how the compiler brings together for a part would be the same as for
a "normal" application in that it starts with a list of classes and finds
their dependencies. The difference with parts would be that the list of
classes in a part would exclude anything already loaded.
Given that a build target collects multiple classes into a few files, then
either (a) each class can exist in exactly one file, or (b) the merged
files have to detect whether a class already exists and not call
qx.Class.define(). Obviously option (a) means the developer has to have a
more detailed knowledge of dependencies, but (b) would make life a lot
easier.
Given also that which parts get loaded in what order would depend on what
a user does, it seems to me that (b) may even be a requirement? I've not
thought this through yet, but I'm wondering if you can analyse the
overlapping sets so that for, say, 5 parts you might end up with say, 20
files - ie broken down into enough granularity that when you request a
specific part, and the partloader knows what parts are already loaded,
there is a specific set of files to load without there being the
possibility of duplicate classes.
Im not sure if that helps, but it might be good to start with looking at
what generate.py does now? Lets keep the conversation going though, I'd
happily talk through ideas :)
Cheers
John
----------------------------------------
From: "Defero" <krosela...@gmail.com>
Sent: Thursday, February 25, 2016 1:26 PM
To: qooxdoo-devel@lists.sourceforge.net
Subject: Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and
100% Javascript API to building applications
Hi John,
so i've been thinking how i would start creating the part loader which
should be "easy" to create with how you set up the things.
But for it to fit our purpose here, it asks that only a single
part/library
can be recompiled.
I'm not sure if there is a nice way of achieving this. In case of two
parts
have the same dependency but are not aware of each other. Which in most UI
qx classes i think shouldn't be an issue if they are compiled/loaded
twice.
But i'm sure there are plenty of classes that have to strictly be loaded
once onto dom.
Do you think there is a way to achieve this without cross-referencing
every
part and adding to boot the same dependencies.
Regards,
Defero
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/QxCompiler-add-ES6-faster-compilation-and-1
00-Javascript-API-to-building-applications-tp7587992p7588112.html
Sent from the qooxdoo mailing list archive at Nabble.com.
----------------------------------------------------------------------------
--
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
