[ https://issues.apache.org/jira/browse/RAVE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erin Noe-Payne updated RAVE-941:
--------------------------------
Description:
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 lieu of
was:
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
> 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: 0.22
>
> 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 lieu of
--
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
|