Bug 1041968 - [RFE][horizon]: Introduce AngularJS as Frontend Javascript Framework
Summary: [RFE][horizon]: Introduce AngularJS as Frontend Javascript Framework
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M1
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact: Ido Ovadia
URL: https://blueprints.launchpad.net/hori...
Whiteboard: upstream_milestone_icehouse-1 upstrea...
Depends On: 1099473 1182533
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:21 UTC by RHOS Integration
Modified: 2015-01-20 09:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-08 15:43:07 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0855 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Dashboard 2014-07-08 19:33:24 UTC

Description RHOS Integration 2013-12-12 20:21:24 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/angularjs-javascript-frontend-framework.

Description:

AngularJS and specifically it's directives are a suitable solution to develop UI features and unify/organize frontend javascript code in Horizon.

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:48:22 UTC
Moving to POST based on upstream status (Implemented).

Comment 3 Ami Jeain 2014-03-19 11:21:44 UTC
more of a framework rather than user flow

Comment 4 Ido Ovadia 2014-03-23 09:33:21 UTC
Does it need QE verificaton?
If yes, please provide any steps?

Comment 5 Julie Pichon 2014-03-24 08:32:12 UTC
I don't think this requires QE verification. This particular blueprint set up the groundwork for using a different Javascript framework and didn't impact on features, from what I can tell from the patch. Thanks.

Comment 8 errata-xmlrpc 2014-07-08 15:43:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0855.html


Note You need to log in before you can comment on or make changes to this bug.