CI to automate build of webrtc tarball for signal-desktop aport
https://gitlab.alpinelinux.org/alpine/aports/-/tree/master/testing/signal-desktop
![]() The layout class is the only class that should have knowledge of page-level constant markup, such as #gutter and #contacts, and should be pretty much the only place we find elements by id (with the exception of template elements). This change removes references to #gutter from views. Rather than hardcoding assumptions about page layout, view elements should ask the layout to insert themselves into the main content area by calling Whisper.Layout.setContent. |
||
---|---|---|
css | ||
images | ||
js | ||
js-deps | ||
nacl | ||
protos | ||
stylesheets | ||
test | ||
background.html | ||
GPL | ||
icon.png | ||
index.html | ||
LGPL | ||
manifest.json | ||
options.html | ||
popup.html | ||
README.md | ||
test.html |
TextSecure Chromium Implementation
This is very early stuff and exists primarily to get the crypto in place. This does not currently work, dont bother trying to use it seriously yet
Getting Started with Development
- Clone the repo
- Open Chrome
- Go to chrome://extensions/
- Enable developer mode (checkbox on the top right)
- Click "Load unpacked extension..."
- Point to the repo's directory
Tests
Please write tests! Our testing framework is mocha and our assertion library is chai:
Tips/Tricks
- Loading the
test.html
page may read, write or clear localStorage. To avoid having to choose between running tests and preserving your existing messages, keys, and other extension data, much of the test suite can be run by starting a local webserver in the repository root, e.g.python -m SimpleHTTPServer
. You can then access the test page athttp://0.0.0.0:8000/test.html
.