[
https://issues.apache.org/jira/browse/RAVE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619101#comment-13619101
]
Chris Geer commented on RAVE-941:
---------------------------------
Erin,
Overall I support using something like AngularJS as the framework but I thought
we had ruled that out [1]. If it ends up being a better fit I agree we should
consider going for it but my concern is the timing. We are on the verge of
releasing 0.21 where we just implemented a new JS API with Backbone and
Handlebars and we are talking about ripping it out already. This poses problems
for implementors who are trying to keep up with recent versions of Rave because
it requires quite a bit of rework (at least potentially).
My recommendation is we move this conversation to the dev list so that we can
discuss further. Thoughts?
[1]
http://mail-archives.apache.org/mod_mbox/rave-dev/201302.mbox/%3CCAENpzYU7Ter_SJrGuJp8rbMyDuwi=bxuogrhytqzaint4cc...@mail.gmail.com%3E
> 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 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
