wine/gecko
0
0
Fork 0
mirror of https://gitlab.winehq.org/wine/wine-gecko.git synced 2024-09-13 09:24:08 -07:00
Code Issues Packages Projects Releases Wiki Activity
574b971d88
gecko/browser/components/loop
History
Mark Banner fedeb471e5 Bug 1030062 Loop Marionette tests need clearer failure points when displayed on tbpl. r=dburns
2014-06-26 09:00:08 +01:00
..
content Bug 914753: Make Emacs file variable header lines correct, or at least consistent. DONTBUILD r=ehsan 2014-06-24 22:12:07 -07:00
standalone Bug 1026504 - Clarify non-shared status of sdk and webl10n for Loop by moving them from the shared libs to non-shared. r=nperriault 2014-06-18 10:43:31 +01:00
test Bug 1030062 Loop Marionette tests need clearer failure points when displayed on tbpl. r=dburns 2014-06-26 09:00:08 +01:00
jar.mn Bug 1026504 - Clarify non-shared status of sdk and webl10n for Loop by moving them from the shared libs to non-shared. r=nperriault 2014-06-18 10:43:31 +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 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 1017394 In MozLoopService use promises rather than callbacks to make the code cleaner. r=mhammond 2014-06-04 14:42:41 +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 1020859 Part 2 - Change Loop to use HawkClient to increase shared code usage and make MozLoopService simpler. r=mhammond 2014-06-18 10:42:15 +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

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.