[Cosmo-dev] Custom dojo build torch passing

[Travis Vachon]

Hi Matthew

Thanks, it was pretty fun to grab this low hanger :) I've answered  
your questions inline..
On Jan 4, 2007, at 10:34 AM, Matthew Eernisse wrote:

>
>
> 1. Are you including your admin UI widget stuff in that build as  
> well? As BCM noted, we need to figure out some sort of strategy for  
> subdividing built JS files (e.g., 'global,' 'login,' 'pim,'  
> 'admin') in a sensible way so that say, normal users aren't hit  
> with the cost of all the stuff for the admin UI. Right now  
> everything goes into 'dojo.js,' but it would be nice to use the  
> same build system to build chunked files.

No, the admin widget stuff is not currently included. As I mentioned,  
unfortunately the build system doesn't currently support that style  
of chunking :(

>
> 2. Does this current, primitive build system eliminate the need to  
> swap out the event/io build of dojo with the widget build? Or is  
> that something that still needs to be done?
>

Good question actually. From the Jared's perspective (that is, the  
perspective of server administrators) no. The final product will be  
using our custom build, so we don't need to deal with stock builds of  
dojo at all.

 From the developer's perspective, however, things a a little more  
complicated. We don't want to wrap our files into the build that  
developers will be using, since this would require rebuilding dojo  
every time we want to see a change we make in the JS. Then again, the  
nature of the build process enforces certain coding practices that  
aren't enforced anywhere else in the process, leading to most of the  
work I needed to do to get our code working in the custom dojo build.  
If we aren't working on the "built" version, we're almost guaranteed  
to introduce one of these bugs somewhere along the way.

I think we might save a lot of time by kicking the particulars of  
this around in a higher bandwidth forum. Next week might provide a  
very good opportunity for that. Any thoughts?

Thanks,

Travis

> Again, thanks a lot for knocking this first part out. Very good work.
>
>
> Matthew
>
>
> Travis Vachon 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.
>> -Travis
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev