[
https://issues.apache.org/jira/browse/RAVE-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jmeas Pls updated RAVE-1109:
----------------------------
Description:
The master branch of Rave is currently a Java webapp with a bit of Javascript
on the side. Per [Rave-941|https://issues.apache.org/jira/browse/RAVE-941] a
goal has been to convert Rave's portal into a full-fledged Angular webapp.
If you've been following 941 you might have seen the angular branch on the Rave
repository, which has had a lot of great work put toward it.
With that said, [~carldanley] noted several issues with the approach taken by
the Angular branch. Because of this, and the fact that @carldanley and I will
be leading development on the Angular portion of the app, this ticket is
intended to replace 941.
The primary issue with the approach on the angular branch is that it wasn't
fully committed in its decision to switch to Angular. Only the gadget portion
of the app had been converted to Angular, while the rest of it was still
managed by JSP and server-side routing with full page refreshes. This approach
was creating a Java webapp with an embedded Angular component more than it was
leading to an entirely-Angular webapp.
Because of this, [~carldanley] have begun work on an updated Angular branch. Of
course, much of the awesome work on the current Angular branch will carry right
over. At first, though, we need to swap out the JSP templates, which might be a
bit jarring at first glance. Soon enough, though, it will be in a familiar
state. For this reason our work will be in a separate branch for now. This
branch can be viewed [on Github|https://github.com/apache/rave/pull/7].
- We'll be expanding on the Grunt build system (already on the Angular branch)
that will allow the client and the server to be developed independently. This
will allow faster iteration on either piece by any developer moving forward.
Down the road, Grunt can be integrated with Maven to continue having a single
command can be run to build the app together.
- Angular UI-Router will manage the client side routes so that there won't be
any hard page refreshes.
- Angular templates will be used in place of JSP
In addition to this, our list of tasks will be added to Jira and Github
throughout this week to track our progress on the project.
To follow along with this epic, I recommend bookmarking [this
link|https://issues.apache.org/jira/browse/RAVE-1115?jql=project%20%3D%20RAVE%20and%20%22Epic%20Link%22%20%3D%20%22Refactor%20Rave%20to%20use%20AngularJS%22].
Also, the PR for these changes is a long-living PR over on
[Github|https://github.com/apache/rave/pull/7].
was:
The master branch of Rave is currently a Java webapp with a bit of Javascript
on the side. Per [Rave-941|https://issues.apache.org/jira/browse/RAVE-941] a
goal has been to convert Rave's portal into a full-fledged Angular webapp.
If you've been following 941 you might have seen the angular branch on the Rave
repository, which has had a lot of great work put toward it.
With that said, [~carldanley] noted several issues with the approach taken by
the Angular branch. Because of this, and the fact that @carldanley and I will
be leading development on the Angular portion of the app, this ticket is
intended to replace 941.
The primary issue with the approach on the angular branch is that it wasn't
fully committed in its decision to switch to Angular. Only the gadget portion
of the app had been converted to Angular, while the rest of it was still
managed by JSP and server-side routing with full page refreshes. This approach
was creating a Java webapp with an embedded Angular component more than it was
leading to an entirely-Angular webapp.
Because of this, [~carldanley] have begun work on an updated Angular branch. Of
course, much of the awesome work on the current Angular branch will carry right
over. At first, though, we need to swap out the JSP templates, which might be a
bit jarring at first glance. Soon enough, though, it will be in a familiar
state. For this reason our work will be in a separate branch for now. This
branch can be viewed [on Github|https://github.com/apache/rave/pull/6].
- We'll be expanding on the Grunt build system (already on the Angular branch)
that will allow the client and the server to be developed independently. This
will allow faster iteration on either piece by any developer moving forward.
Down the road, Grunt can be integrated with Maven to continue having a single
command can be run to build the app together.
- Angular UI-Router will manage the client side routes so that there won't be
any hard page refreshes.
- Angular templates will be used in place of JSP
In addition to this, our list of tasks will be added to Jira and Github
throughout this week to track our progress on the project.
To follow along with this epic, I recommend bookmarking [this
link|https://issues.apache.org/jira/browse/RAVE-1115?jql=project%20%3D%20RAVE%20and%20%22Epic%20Link%22%20%3D%20%22Refactor%20Rave%20to%20use%20AngularJS%22].
Also, the PR for these changes is a long-living PR over on
[Github|https://github.com/apache/rave/pull/6].
> Refactor Rave to use AngularJS
> ------------------------------
>
> Key: RAVE-1109
> URL: https://issues.apache.org/jira/browse/RAVE-1109
> Project: Rave
> Issue Type: Epic
> Reporter: Jmeas Pls
>
> The master branch of Rave is currently a Java webapp with a bit of Javascript
> on the side. Per [Rave-941|https://issues.apache.org/jira/browse/RAVE-941] a
> goal has been to convert Rave's portal into a full-fledged Angular webapp.
> If you've been following 941 you might have seen the angular branch on the
> Rave repository, which has had a lot of great work put toward it.
> With that said, [~carldanley] noted several issues with the approach taken by
> the Angular branch. Because of this, and the fact that @carldanley and I will
> be leading development on the Angular portion of the app, this ticket is
> intended to replace 941.
> The primary issue with the approach on the angular branch is that it wasn't
> fully committed in its decision to switch to Angular. Only the gadget portion
> of the app had been converted to Angular, while the rest of it was still
> managed by JSP and server-side routing with full page refreshes. This
> approach was creating a Java webapp with an embedded Angular component more
> than it was leading to an entirely-Angular webapp.
> Because of this, [~carldanley] have begun work on an updated Angular branch.
> Of course, much of the awesome work on the current Angular branch will carry
> right over. At first, though, we need to swap out the JSP templates, which
> might be a bit jarring at first glance. Soon enough, though, it will be in a
> familiar state. For this reason our work will be in a separate branch for
> now. This branch can be viewed [on
> Github|https://github.com/apache/rave/pull/7].
> - We'll be expanding on the Grunt build system (already on the Angular
> branch) that will allow the client and the server to be developed
> independently. This will allow faster iteration on either piece by any
> developer moving forward. Down the road, Grunt can be integrated with Maven
> to continue having a single command can be run to build the app together.
> - Angular UI-Router will manage the client side routes so that there won't be
> any hard page refreshes.
> - Angular templates will be used in place of JSP
> In addition to this, our list of tasks will be added to Jira and Github
> throughout this week to track our progress on the project.
> To follow along with this epic, I recommend bookmarking [this
> link|https://issues.apache.org/jira/browse/RAVE-1115?jql=project%20%3D%20RAVE%20and%20%22Epic%20Link%22%20%3D%20%22Refactor%20Rave%20to%20use%20AngularJS%22].
> Also, the PR for these changes is a long-living PR over on
> [Github|https://github.com/apache/rave/pull/7].
--
This message was sent by Atlassian JIRA
(v6.2#6252)
