Loop/Architecture: Difference between revisions
< Loop
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
These technology choices will be moved into one of the preceding sections as decisions are made: | These technology choices will be moved into one of the preceding sections as decisions are made: | ||
* Localization ({{bug|972884}}) | * Localization ({{bug|972884}}) | ||
* Client MVC Library ({{bug|975548}}) | * Client MVC Library + associated libs ({{bug|975548}}) | ||
* Client CSS toolkit (if any) ({{bug|975548}}) | |||
* Client side unit-testing framework ({{bug|976127}}) | |||
* Client-driven end-to-end framework ({{bug|976134}}) | |||
* Standalone-page CSS toolkit (if any) | |||
* Standalone-page unit-testing framework ({{bug|976133}}) | |||
* Standalone-page end-to-end system testing framework ({{bug|976134}}) | |||
= Network Architecture = | = Network Architecture = | ||
Revision as of 23:45, 25 February 2014
Design Goals
Underlying Technologies
Mozilla Technologies
The Loop project relies on a number of other technologies under development within Mozilla. These include the following:
Third-Party Technologies
- Node.js for Loop server, at least through production
Open Issues
These technology choices will be moved into one of the preceding sections as decisions are made:
- Localization (bug 972884)
- Client MVC Library + associated libs (bug 975548)
- Client CSS toolkit (if any) (bug 975548)
- Client side unit-testing framework (bug 976127)
- Client-driven end-to-end framework (bug 976134)
- Standalone-page CSS toolkit (if any)
- Standalone-page unit-testing framework (bug 976133)
- Standalone-page end-to-end system testing framework (bug 976134)