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] [Updated] (RAVE-941) Refactor rave portal as an angularjs web application
Date Tue, 09 Jul 2013 17:47:48 GMT

     [ https://issues.apache.org/jira/browse/RAVE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erin Noe-Payne updated RAVE-941:
--------------------------------

    Fix Version/s:     (was: 0.22)
                   1.0
    
> Refactor rave portal as an angularjs web application
> ----------------------------------------------------
>
>                 Key: RAVE-941
>                 URL: https://issues.apache.org/jira/browse/RAVE-941
>             Project: Rave
>          Issue Type: Epic
>            Reporter: Erin Noe-Payne
>            Assignee: Erin Noe-Payne
>             Fix For: 1.0
>
>   Original Estimate: 1m
>  Remaining Estimate: 1m
>
> With RAVE-914 we now have the rave core functionality isolated from the portal. This
allows us to refactor the portal application and write it as a reference implementation on
top of the rave core with the following goals:
> - Support generic data contexts for pages - portal, profile, portfolio or whatever else.
No more hard coded portal page vs profile page. 
> - Allow implementers to extend the portal application with less reliance on overlays.
> - Move away from jsps or other heavy-lifting view rendering logic from the server.
> I'm proposing to use angularjs (http://angularjs.org/) as a client side mvc framework.
This would be in place of previous efforts to implement the portal using backbonejs and handlebars.
Basic roadmap:
> - Move away from jsp's, either moving to a lighter-weight rendering framework or consider
serving only raw html with no rendering framework on the server at all.
> - Rewrite / update portal's views as angularjs compatible markup.
> - Write the portal js as an angularjs application that interacts with the rave core.

> - Use the new rest apis to serve data for client side navigation and partial view loads.
> - Allow implementers to extend rave portaljs for custom functionality without overlaying,
allow them to add views for new custom contexts without requiring overlays.

--
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

Mime
View raw message