[Cosmo-dev] Custom dojo build torch passing

[Matthew Eernisse]

Travis,

First of all, thanks for all the work you've done on this. This is a 
huge step toward improving the overall feeling of pokeyness in the app.

Right now, optimizing for the main UI page shouldn't be so much of an 
issue, since it essentially just means you're precaching stuff as the 
user hits the login page. We're assuming people are coming to the login 
page with the intent of logging in and using the app, so we take the hit 
at the login page, or as we load the main UI -- either way, you still 
have to load it.

A couple of questions:

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.

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?

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