[Cosmo-dev] Custom dojo build torch passing

[Travis Vachon]

Yeah, that would be the ideal.

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.

-Travis

On Jan 3, 2007, at 5:27 PM, Brian Moseley wrote:

> On 1/3/07, Travis Vachon <travis at osafoundation.org> wrote:
>
>> The situation on the login page is similar, though a few more
>> requests since the build is currently optimized for the calendar ui.
>> This brings up an interesting question: which page should we optimize
>> our main build for? In reality, it probably won't make a huge huge
>> difference, but it would be nice to have at least some guiding
>> principle.
>
> maybe we should build one file of common code, one file of calendar
> code, and one file of login code?
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev