Commit Graph

4 Commits

Author SHA1 Message Date
Cao Xuan Hoang b01c028673 Add Apache 2.0 license to source file
As per OpenStack licensing guide lines [1]:
[H102 H103] Newly contributed Source Code should be licensed under
the Apache 2.0 license.

[1] http://docs.openstack.org/developer/hacking/#openstack-licensing

Change-Id: If9ae2195d23ee8ed4bfe3da136e647f4e291a415
2016-12-02 17:40:28 +07:00
Thai Tran 35e47358f0 Fix bug where WEBROOT is not respected
The WEB_ROOT setting needs to be respected rather than assuming / as
the root of the application. Simiarly, we can not assume that STATIC_URL
is a sub url of the WEB_ROOT. They can be configured as two indepedent url.

Angular templates are loaded dynamically with Ajax, which requires an
absolute base path. We define those base paths as angular constants for
template use and future routing.

TO TEST, follow directions at:
  http://docs.openstack.org/developer/horizon/topics/settings.html#webroot

Co-Authored-By: Matt Borland <matt.borland@hp.com>
Co-Authored-By: Shaoquan Chen <sean.chen2@hp.com>
Co-Authored-By: Thai Tran <tqtran@us.ibm.com>

Change-Id: Ifcd459633682edc94b270019ce77e17d64bea22d
Closes-Bug: #1451681
2015-07-22 04:10:50 +00:00
Shaoquan Chen 3c0ff6f398 Improving readability for Horizon top module structure
This patch improves the readability on how Horizon's application
level module `hz.app` is composited and how its dependency modules
are organized.  The dependency modules come from three sources:

1) Library modules - modules defined in third-party libraries,
   including angular's extensions
2) Horizon's built-in modules, including modules from `framework`
   components and modules from `openstack_dashboard` application
   core components.
3) Horizon's plug-in modules - modules from Horizon's extensions
   components via Horizon's plug-in mechanism.

Horizon's built-in modules are managed as a couple of trees, then only
the top modules of each tree should be listed in the Horizon's built-in
modules.

Change-Id: I989a0b5cc8b24f6b168629f4a8fa5e485dcf1a2d
Closes-Bug: #1472098
2015-07-07 14:36:15 -07:00
Matt Borland 241c2cf432 Get unit tests working with Karma
Establish features for running Karma tests.  Separate karma configurations
are used due to current overlap of template file structure.

You can run the karma tests via:
  ./run_tests.sh --karma

The Karma framework allows for many features like unit test coverage and
provides a common configuration for different test runners.

Change-Id: I79680ef6369383c148da68e6677945886a48df81
Implements: blueprint karma
2015-06-01 14:14:58 +00:00