gecko/browser/components/loop
2014-07-01 17:12:54 +01:00
..
content Bug 1023507 - Handle SDK failures when calling connect. r+ui-r=dmose 2014-06-25 11:00:00 -04:00
standalone Bug 1023507 - Handle SDK failures when calling connect. r+ui-r=dmose 2014-06-25 11:00:00 -04:00
test Bug 1026782 Implements MozLoopService.setLoopCharPref. r=ttaubert 2014-07-01 17:12:54 +01:00
jar.mn Bug 1011472 - Add audio alert for incoming call r=florian,standard8 2014-06-26 18:55:03 -05:00
manifest.ini Bug 994483 Add Loop unit tests to tbpl. r=dburns 2014-06-05 15:45:16 +01:00
moz.build Bug 1022689 Separate out the Loop Push Handler from the Loop Service code to help similify testing and clarify separation of modules. r=mhammond 2014-06-16 08:41:17 +01:00
MozLoopAPI.jsm Bug 1026782 Implements MozLoopService.setLoopCharPref. r=ttaubert 2014-07-01 17:12:54 +01:00
MozLoopPushHandler.jsm Bug 1022689 Separate out the Loop Push Handler from the Loop Service code to help similify testing and clarify separation of modules. r=mhammond 2014-06-16 08:41:17 +01:00
MozLoopService.jsm Bug 1026782 Implements MozLoopService.setLoopCharPref. r=ttaubert 2014-07-01 17:12:54 +01:00
README.txt Bug 994485 Update loop's readme and remove redundant make-links.sh DONTBUILD 2014-05-29 22:12:30 +01:00

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.