rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erin Noe-Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RAVE-954) Develop strategy for resource bundling without jsp
Date Thu, 18 Apr 2013 15:17:17 GMT

    [ https://issues.apache.org/jira/browse/RAVE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635234#comment-13635234

Erin Noe-Payne commented on RAVE-954:

Some ideas I have been bouncing around - 

- Have each context write some sort of config (js variable, json file, xml file or whatever)
defining the bundles that context requires. Then write an angular directive that loads the
defined bundles - minifying and concat'ing depending on the current portal preferences.
- Use requirejs r.js optimizer to build and optimize dependency trees. 
> Develop strategy for resource bundling without jsp
> --------------------------------------------------
>                 Key: RAVE-954
>                 URL: https://issues.apache.org/jira/browse/RAVE-954
>             Project: Rave
>          Issue Type: Sub-task
>            Reporter: Erin Noe-Payne
>             Fix For: 0.22
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> As we move away from jsp, we need a new strategy for bundling static resources (js, css)
for concat and minification. 
> Key issues: 
> - With js debug set off, individual files need to be loaded
> - With js debug on, concat & minified files should be loaded
> - As implementers add new contexts, they should be able to dynamically declare new bundles
based on the dependency tree of the single-page app for their context

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message