gecko-dev/browser/components/loop
Mark Banner f33dc16c20 Bug 1144344. r=mikedeboer 2015-03-18 12:43:56 +00:00
..
content Bug 1144344. r=mikedeboer 2015-03-18 12:43:56 +00:00
standalone Bug 1047040 - Add browser-specific graphic of GUM prompt to the media-wait message. r=dmose 2015-02-23 13:00:03 -05:00
test Bug 1144344. r=mikedeboer 2015-03-18 12:43:56 +00:00
ui Bug 1088672 - Part 8. Rewrite Loop's incoming call handling in the flux style. Update the ui-showcase. r=mikedeboer 2015-03-12 14:01:38 +00:00
.gitignore Bug 1044796 Provide an option to Loop's standalone client makefile to create a version.txt file. r=nperriault 2014-07-30 17:13:16 +01:00
CardDavImporter.jsm Bug 972079 - CardDAV Address Importer for Loop r=MattN 2014-08-29 13:31:46 -05:00
GoogleImporter.jsm Bug 1089011: make sure to only import contacts that are part of the default contacts group. r=MattN 2014-10-29 17:40:57 +01:00
LoopCalls.jsm Bug 1140092 - Remove handling of guest calls from the Loop backend. r=mikedeboer 2015-03-09 23:42:08 +00:00
LoopContacts.jsm Bug 1079941: implement LoopContacts.search to allow searching for contacts by query and use that to find out if a contact who's trying to call you is blocked. r=abr 2014-10-16 16:35:10 +02:00
LoopRooms.jsm Bug 1080953 - UITour: tell page when first incoming call is received and if that room window is open. r=dmose,dolske 2014-12-17 22:37:19 -05:00
LoopStorage.jsm Bug 1078309: use a different database for each Fx Account. r=abr,paolo 2014-10-09 13:11:24 +02:00
MozLoopAPI.jsm Bug 1141059: ignore attempts to share e10s tabs in a Hello conversation. r=Standard8 2015-03-10 10:43:44 +01:00
MozLoopPushHandler.jsm Bug 1099296 - Attach LoadInfo to remaining callers of ioService and ProtocolHandlers - websocket changes in browser/ (r=gavin) 2015-02-17 10:10:06 -08:00
MozLoopService.jsm Bug 1132293 - Let reliers access derived encryption keys through FxAccountsOAuthClient. r=mhammond 2015-03-09 21:46:00 -04:00
MozLoopWorker.js Bug 998989 - anonymize sensitive data in telemetry log. r=ekr, r=dveditz 2014-07-10 19:53:44 -04:00
README.txt Bug 1125775 - Add information about the front-end unit tests and ui-showcase to Loop's README.txt. DONTBUILD as NPOTB. r=nperriault 2015-01-26 18:56:20 +00:00
build-jsx Bug 1045690 Ensure the correct version of react is used when building the Loop jsx files. r=Standard8 2014-09-16 11:38:59 +01:00
jar.mn Bug 1096399 - [Loop] Upgrade React to 0.12.2. r=Standard8 2015-01-06 13:07:26 +01:00
manifest.ini Bug 1088006 - Hook up Loop's ui-showcase to unit tests so that we don't keep on breaking it, and so that it can possibly catch use of es6 errors. r=dmose 2015-03-12 08:04:51 +00:00
moz.build Bug 1139427 - Define file-based metadata in /browser/components. r=gavin 2015-03-08 20:43:22 +01:00
run-all-loop-tests.sh Bug 1113346-update loop test runner script, rs=MattN, NPOTB, DONTBUILD 2014-12-18 14:10:17 -08:00

README.txt

This is the directory for the Loop desktop implementation and the standalone
client.

The desktop implementation is the UX built into Firefox, activated by the Loop
button on the toolbar. The standalone client is the link-clicker UX for any
modern browser that supports WebRTC.

The standalone client is a set of web pages intended to be hosted on a
standalone server referenced by the loop-server.

The standalone client exists in standalone/ but shares items
(from content/shared/) with the desktop implementation. See the README.md
file in the standalone/ directory for how to run the server locally.

Working with React JSX files
============================

Our views use [React](http://facebook.github.io/react/) written in JSX files
and transpiled to JS before we commit. You need to install the JSX compiler
using npm in order to compile the .jsx files into regular .js ones:

    npm install -g react-tools

Once installed, run build-jsx with the --watch option from
browser/components/loop, eg.:

    cd browser/components/loop
    ./build-jsx --watch

build-jsx can also be do a one-time compile pass instead of watching if
the --watch argument is omitted.  Be sure to commit any transpiled files
at the same time as changes to their sources.


Hacking
=======
Please be sure to execute

  browser/components/loop/run-all-loop-tests.sh

from the top level before requesting review on a patch.


Front-End Unit Tests
====================
The unit tests for Loop reside in three directories:

- test/desktop-local
- test/shared
- test/standalone

You can run these as part of the run-all-loop-tests.sh command above, or you can run these individually in Firefox. To run them individually, start the standalone client (see standalone/README.md) and load:

  http://localhost:3000/test/


Functional Tests
================
These are currently a work in progress, but it's already possible to run a test
if you have a [loop-server](https://github.com/mozilla-services/loop-server)
install that is properly configured.  From the top-level gecko directory,
execute:

  export LOOP_SERVER=/Users/larry/src/loop-server
  ./mach marionette-test browser/components/loop/test/functional/manifest.ini

Once the automation is complete, we'll include this in run-all-loop-tests.sh
as well.


UI-Showcase
===========
This is a tool giving the layouts for all the frontend views of Loop, allowing debugging and testing of css layouts and local component behavior.

To access it, start the standalone client (see standalone/README.md) and load:

  http://localhost:3000/ui/