-
Task
-
Resolution: Duplicate
-
Minor
-
None
-
None
-
None
I stumbled upon ng-boilerplate last night, which seems to be a slightly more scalable way to lay out your angular project.
Our current source for the Workbench is organized into a single monolithic module:
gui/js/
|
| - app/
|
| - app.js
|
| - view1/
|
| - Controller1.js
|
| - view1.html.js
|
| - view2/
|
| - Controller2.js
|
| - view2.html.js
|
| - view3/
|
| - Controller3.js
|
| - view3.html.js
|
A much more scalable and reusable approach might be something like this:
js/
|
| - module1/
|
| - Controller.js/
|
| - partials/
|
| - view1.html
|
| - view2.html
|
| - module2/
|
| - controllers/
|
| - Controller3.js
|
| - Controller4.js
|
| - Controller5.js
|
| - Controller6.js
|
| - partials/
|
| - view3.html
|
| - view4.html
|
| - view5.html
|
| - view6.html
|
| - module3/
|
| - Controller7.js
|
| - Controller8.js
|
| - partials/
|
| - view3.html
|
| - view4.html
|
This ticket is complete when we have organized the Workbench UI source code into modules that can be more easily reused. LoginModule is one that would be very useful if we ever decide to extend the platform with a second interface (i.e. Admin UI).
- is duplicated by
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
NDS-229 Investigate removing Bower from the frontend build chain to support Browserify
-
- Closed
-
