Hey,
while I agree in general, that the size should be small, I think, that
if you want all functionality, then you get all functionality, and
QooxDoo has a looooooot to offer ( thankfully ).
There are other things you should consider
1) A normal jpeg can be between 1 and 4MB, so 2MB is not that big
considering things ppl do now with Netflix and YouTube.
2) If you load all functionality, then stay on the same page, I.e. load
only once and use WebSokets or Ajax for communication to the BE. The
browser will also help with caching as long as you don't do things like
qx.js?date=123, or a hard re-load
3) Client side storage may be another option to consider to help speed
things up ( haven't tried that one yet myself but ... )
4) you can exclude things you don't need. I.e do you need Tree, and
VirtualTree, and TreeVirtual ?
5) Load on demand. I.e. bundle logical classes together and only load
them into the browser if needs be.
For my app, build-all is the perfect solution, for others load on demand
may be better. However the flexibility is there to morph QooxDoo the way
you need/want it to be.
To your second point, that is a sore spot. QooxDoo, as an API should
remain as consistent as possible. I think it does receive too many
changes to the existing API already.
Every time you're getting rid of a functionality you will make it that
much harder for applications to move along and stay current. This is
probably why there are so many 'old' apps out there which were never
updated. Aka. Bit Rot.
So my suggestion would be to be very careful with a survey and removing
bits and pieces. I would only do this for major revisions and not for
point releases.
Just my 2c.
Varol
On 12/11/2013 02:56 AM, Petr Kobalíc(ek wrote:
Hi guys,
I think that the build-all job is not an ideal solution - it builds
everything resulting in a really huge js file. Customized builds are
always problematic and it requires a lot of tweaking to decrease the
size of the resulting script. I was able to decrease the recent
qooxdoo into 1.4MB, but it grows with every new version.
I think that there should be some cleanup removing all unnecessary
things, maybe survery "which features in qooxdoo do you use" can help
for future directions.
Best,
Petr
On Mon, Dec 9, 2013 at 5:47 PM, thron7 <[email protected]
<mailto:[email protected]>> wrote:
On Mon, Dec 9, 2013 at 4:15 PM, Martin Wittemann
<[email protected] <mailto:[email protected]>> wrote:
> Hey,
>
> In qooxdoo desktop you usually have to develop using the SDK and
then
> "build" your app.
>
> Is there a way to generate something like a qooxdoo.js file with
the whole
> library inside so that you can script script it as you like
(like jqueryui
> or dojo)? Actually it could be nice to have every widget loaded
at runtime
> like dojo's require("dojo.button") but both the approaches would
be nice,
> just avoiding the build phase.
>
> I hope the question is understandable :) Thank you everybody!
>
>
> We do have a build in job for including all classes in a source /
> development version. Simply use the ‚source-all‘ job in a
skeleton and your
> done. For a build / optimized version of qooxdoo, you can go to the
> framework folder and edit the config.json file to get that done.
There is
> already a job (build-all) define doing that but its not
exported. Write the
> job-name in the export section and invoke that job using the
generator. This
> will result in a large file (2MB) in the build/script folder
which might be
> what your looking for.
The latter option (the unsupported 'build-all' job) is probably more
what you're looking for. The former approaches Martin mentions will
not generate a self-contained library file you can program against
(and this is how I understand your question). But as qooxdoo
applications run against the framework's runtime (ie. there is a main
runtime that manages your application code), a stand-alone library
might not work as expected even if it contains all framework classes.
But there are others on this list who have more experience with
tweaking the resulting script.
T.
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
