Changes

Jump to: navigation, search

Loop/Architecture

374 bytes removed, 13:34, 24 August 2015
Underlying Technologies: Update for current technologies
= Underlying Technologies =
 
== Mozilla Technologies ==
* [[Identity/Firefox Accounts|Firefox Accounts]]
* [[WebAPI/SimplePush|Simple Push]] ({{bug|976789}})
* [[Labshttps://developer.mozilla.org/en-US/SocialAPI|Social API]docs/Mozilla/QA/Marionette Marionette] for functional testing ({{bug|971987}})** '''''Note''': Waiting for feedback from Desktop team about modifications to current Social API approach; may be re-using Social components without being a literal Social provider. Feedback due no include selenium later than 25-Apr-2014.''* Marionette ), and for automating client-side running unit tests for build-system & tbpl ({{bug|976127}})test framework.
== Third-Party Technologies ==
* [http://facebook.github.io/react/ React]* [http://backbonejs.org/ Backbone] (being phased out)* Node.js for Loop server, at least through production* webl10n for Localization , extracted from gaia ({{bug|972884}})* [http://eslint.org/ eslint] for linting javascript
* Mocha and Chai for client-side and standalone-page unit-testing framework ({{bug|976133}})
* Not using client CSS toolkit at the moment (this may be revisited) ({{bug|976854}}, {{bug|976857}})
 
== Open Issues ==
These technology choices will be moved into one of the preceding sections as decisions are made:
* Client MVC Library + associated libs ({{bug|975548}}) -- Probably Backbone
* Client-driven end-to-end framework ({{bug|976114}})
* Standalone-page end-to-end system testing framework ({{bug|976134}})
= Network Architecture =
Canmove, confirm, emeritus
3,627
edits

Navigation menu