gecko/browser/components/loop
2014-06-05 10:51:37 -05:00
..
content Bug 1021036 - Change default button color from grey to purple r=NiKo` 2014-06-05 10:51:37 -05:00
standalone Bug 987086 Loop web client should use configuration for determining server url. r=nperriault, r=Standard8 2014-06-05 15:18:41 +02:00
test Bug 994483 Add Loop unit tests to tbpl. r=dburns 2014-06-05 15:45:16 +01:00
jar.mn Backed out changeset 3540ecf33808 / bug 1003029 due to test failures. 2014-06-04 13:16:06 +01:00
manifest.ini Bug 994483 Add Loop unit tests to tbpl. r=dburns 2014-06-05 15:45:16 +01:00
moz.build Bug 1000007 Separate out loop from the social api, and add a loop specific service and API injection. r=mhammond 2014-05-29 21:13:46 +01:00
MozLoopAPI.jsm Bug 1017394 In MozLoopService use promises rather than callbacks to make the code cleaner. r=mhammond 2014-06-04 14:42:41 +01:00
MozLoopService.jsm Bug 1017902 Use saved hawk session tokens, if possible, when registering with the server to preserve the session across restarts. r=jparsons,r=mhammond 2014-06-05 10:29: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.