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-941) Refactor rave portal as an angularjs web application
Date Mon, 01 Apr 2013 19:49:16 GMT

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

Erin Noe-Payne commented on RAVE-941:
-------------------------------------

Yeah good question. I've updated the description to have some more specific info about my
vision - so all please give input.

Basically the Backbone / Handlebars effort was my thought process for updating the portal
before our apachecon meetup. Now we've gone down the road of specifically isolating the rave
core and writing better rest apis, and treating the rave portal as a reference implementation
on top of core. In this scenario I see angular as a much better fit.

If we go the route of using angular I will end up backing out backbone and handlebars and
pass control of all state management & client side templating over to angular.

In terms of branching, I can go either way. As an angular app it is only looking to serve
html, so we can easily build out the angular app along a different set of url paths than the
current portal much as we are doing with the rest apis. It may be weird to deliver that incomplete
content as part of the trunk though.
                
> 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

Mime
View raw message