[Cosmo-dev] Custom dojo build torch passing

[Matthew Eernisse]

I was lurking yesterday in #dojo-meeting, and they talked a bit about 
the linker, as well as the doc extractor, which both seem to be kind of 
stalled. They were talking about what they can do to push those project 
forward.

It sounds like that'll be a topic at the upcoming Dojo Developer Day 
(1/12-13). The other topic specifically mentioned was a presentation 
from Alex about major changes to the widget system to deal with bloat 
and bad performance.

Here's the plan for '3D2':

http://dojotoolkit.org/pipermail/dojo-contributors/2006-December/005701.html


Matthew

Nicola Piccinini wrote:
> 
>> Unfortunately, the dojo build system isn't terribly sophisticated yet. 
>> The way it works now, each of those files would be built with all of 
>> the required dependencies, which means a good deal of code would be 
>> duplicated in each.
>>
>> This particular problem is actually a manifestation of the fact that 
>> there is no way to specifically exclude certain modules from a build. 
>> That is, if a module is dojo.required by any file in the build, its 
>> code will always be sucked in as well. Solving this problem would be 
>> an interesting and, I imagine, useful contribution to the dojo 
>> project, but would take a number of cycles that we may want to use 
>> elsewhere for now.
> 
> as far as I know the jslinker subproject (in dojo/tools) is aimed to 
> solve this problems but it doesn't seem under active development (last 
> change is dated 2006-10-06)
>