support for custom version of yui at the app level

[caridy]

• by using npm i yui@<some-version> in the app folder, at the same level then mojito, it will force mojito to rely on that version of yui.
• a warning message will be issued to announce the detection of the new yui version.
• this version will affect server and client.
• for customization of the client side only for online apps, you can use application.json->yui->config settings instead.

TODO:

• test this in manhattan
• add unit test

[caridy]

/cc @ItsAsbreuk @sdesai

[mojit0]

+1

[drewfish]

This is the part that I suspect will fail in Manhattan. In Manhattan the server handles multiple apps, and so doesn't cd to any particular app directory at startup.

[ItsAsbreuk]

I hope this also involves custom base location at the client side other than used on the client side.
Because situations may exist where clientside loads from a custom comboloader through ssl. The serverside doesn't need to (preferably not).

Marco.

[caridy]

@ItsAsbreuk that's already covered with the new yui->config->seed and yui->config->base / comboBase / root, they are not affecting the server side execution, only the client side. I showed an example during my yuiconf presentation, here is the link of the gist:

https://gist.github.com/4070536#file_custom_seed_2.json

[ItsAsbreuk]

Caridy, you are great!
I haven;t seen your presentation yet. I've started looking at your sheets (http://www.slideshare.net/caridy/yuiconf2012-mojito-for-yui-developers) right now :)

Regards,
Marco.

[drewfish]

Hi everyone,

The develop-perf branch just went away, and github auto-closed pull requests against it. You'll have to redo this pull request against the develop branch. Sorry about this.

Drew