headers
Yoshiroh Kamiyama | 7 Jul 2011 07:13
Picon

Re: dojo.js size increase (1.6 --> 1.7)

Looks very good analysis.

Splitting files into smaller pieces is, in general, a good idea.
But I think it is truly beneficial only when those pieces are independent and optional, and user app can selectively pick up only necessary pieces.
Otherwise, as Bill pointed out, it ends up introducing additional overhead, such as deps lists or module return values.
For example, my app does not use the code in dojo/dom/form and dojo/mouse. How can I exclude them from my build?
Deep and strict inter-module dependencies are preventing doing something like that.
If we could do such a thing, I think the code size issue would be mitigated.
--
ykami
_______________________________________________
dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
Permalink | Reply |

Gmane