[Cosmo-dev] Re: [commits-cosmo] (mde) [2934] Fixed dueling-stylesheets issue in login page, removed old Cosmo Ui boilerplating.

[Matthew Eernisse]

Good call. I agree that the custom-tag approach will be very useful for 
pages that follow a truly boilerplated layout, or for pieces of 
ubiquitous functional boilerplate like the Dojo stuff we'll need on 
multiple pages.

There will still likely be pages that don't conform to a standard layout 
-- in those cases you either have to start doing mods to your standard 
layout boilerplate for each exception, or just blowing off the standard 
layout tags. The special-purpose pages like the login and the end-user 
calendar view are likely going to be in the exception category -- and I 
suspect there may be more as we end up with more 'single-page app' 
components in the app.

Whatever layout boilerplating scheme we go with, it needs to plug into 
the same skinning framework that the client-side JS code does -- which 
probably means setting the template-directory path in the server-side code.


Matthew


Travis Vachon wrote:
> I think this approach could be used for the dojo boilerplate as well. 
> I've created "dojoBoilerplate.tag" in my working copy which serves the 
> exact same function as including dojo.jsp currently. I think it might be 
> nice to establish this as our standard approach for bringing in 
> boilerplate on the server side, leaving JSPs to contain our content, 
> though I'm very open to suggestions as far as this approach is 
> concerned! Another example would be the global css kludge being 
> discussed in another thread, which would be brought in only when it's 
> needed.