diff --git a/.travis.yml b/.travis.yml
new file mode 100644
index 00000000..ba1cf0ac
--- /dev/null
+++ b/.travis.yml
@@ -0,0 +1,22 @@
+language: node_js
+node_js:
+ - "0.8"
+install:
+ - "bin/installDeps.sh"
+ - "export GIT_HASH=$(cat .git/HEAD | head -c 7)"
+before_script:
+ - "tests/frontend/travis/sauce_tunnel.sh"
+script:
+ - "tests/frontend/travis/runner.sh"
+env:
+ global:
+ - secure: "oKA4KbSvyxMOFCiOa3hWswnaIrCmX60MfhBhD8xu8sodOqbdK5RUrxDJew9p\n1nNSewxoVmKhX0G5GxIABfGtdU1nrEzCEoejTDJIFmzEbcLcHpcyarouWLSY\nOpn11FKS1rnb69aflHM7K8l4dhrCkA2i0Dwwl8LN3HayGzDV2Rg="
+ - SAUCE_USER=pita
+jdk:
+ - oraclejdk6
+notifications:
+ email:
+ - petermartischka@googlemail.com
+ irc:
+ channels:
+ - "irc.freenode.org#etherpad-lite-dev"
\ No newline at end of file
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 613cd896..abcf0a21 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,16 @@
+# v1.2
+ * Internationalization / Language / Translation support (i18n) with support for German/French
+ * A frontend/client side testing framework and backend build tests
+ * Customizable robots.txt
+ * Customizable app title (finally you can name your epl instance!)
+ * eejs render arguments are now passed on to eejs hooks through the newly introduced `renderContext` argument.
+ * Plugin-specific settings in settings.json (finally allowing for things like a google analytics plugin)
+ * Serve admin dashboard at /admin (still very limited, though)
+ * Modify your settings.json through the newly created UI at /admin/settings
+ * Fix: Import
's as 's and not as
's!
+ * Added solaris compatibility (bin/installDeps.sh was broken on solaris)
+ * Fix a bug with IE9 and Password Protected Pads using HTTPS
+
# v1.1.5
* We updated to express v3 (please [make sure](https://github.com/visionmedia/express/wiki/Migrating-from-2.x-to-3.x) your plugin works under express v3)
* `userColor` URL parameter which sets the initial author color
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5f081f27..b0fff543 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,49 +1,56 @@
# Developer Guidelines
-
-Please talk to people on the mailing list before you change this page
-
-Mailing list: https://groups.google.com/forum/?fromgroups#!forum/etherpad-lite-dev
-
-IRC channels: [#etherpad](irc://freenode/#etherpad) ([webchat](webchat.freenode.net?channels=etherpad)), [#etherpad-lite-dev](irc://freenode/#etherpad-lite-dev) ([webchat](webchat.freenode.net?channels=etherpad-lite-dev))
+(Please talk to people on the mailing list before you change this page, see our section on [how to get in touch](https://github.com/ether/etherpad-lite#get-in-touch))
**Our goal is to iterate in small steps. Release often, release early. Evolution instead of a revolution**
## General goals of Etherpad Lite
-* easy to install for admins
-* easy to use for people
+To make sure everybody is going in the same direction:
+* easy to install for admins and easy to use for people
+* easy to integrate into other apps, but also usable as standalone
* using less resources on server side
-* easy to embed for admins
-* also runable as etherpad lite only
-* keep it maintainable, we don't wanna end ob as the monster Etherpad was
* extensible, as much functionality should be extendable with plugins so changes don't have to be done in core
+Also, keep it maintainable. We don't wanna end ob as the monster Etherpad was!
-## How to code:
-* **Please write comments**. I don't mean you have to comment every line and every loop. I just mean, if you do anything thats a bit complex or a bit weird, please leave a comment. It's easy to do that if you do while you're writing the code. Keep in mind that you will probably leave the project at some point and that other people will read your code. Undocumented huge amounts of code are worthless
-* Never ever use tabs
-* Indentation: JS/CSS: 2 spaces; HTML: 4 spaces
-* Don't overengineer. Don't try to solve any possible problem in one step. Try to solve problems as easy as possible and improve the solution over time
-* Do generalize sooner or later - if an old solution hacked together according to the above point, poses more problems than it solves today, reengineer it, with the lessons learned taken into account.
-* Keep it compatible to API-Clients/older DBs/configurations. Don't make incompatible changes the protocol/database format without good reasons
-
-## How to work with git
-* Make a new branch for every feature you're working on. Don't work in your master branch. This ensures that you can work you can do lot of small pull requests instead of one big one with complete different features
-* Don't use the online edit function of github. This only creates ugly and not working commits
-* Test before you push. Sounds easy, it isn't
-* Try to make clean commits that are easy readable
-* Don't check in stuff that gets generated during build or runtime (like jquery, minified files, dbs etc...)
-* Make pull requests from your feature branch to our develop branch once your feature is ready
+## How to work with git?
+* Don't work in your master branch.
+* Make a new branch for every feature you're working on. (This ensures that you can work you can do lots of small, independent pull requests instead of one big one with complete different features)
+* Don't use the online edit function of github (this only creates ugly and not working commits!)
+* Try to make clean commits that are easy readable (including descriptive commit messages!)
+* Test before you push. Sounds easy, it isn't!
+* Don't check in stuff that gets generated during build or runtime
* Make small pull requests that are easy to review but make sure they do add value by themselves / individually
-## Branching model in Etherpad Lite
+## Coding style
+* Do write comments. (You don't have to comment every line, but if you come up with something thats a bit complex/weird, just leave a comment. Bear in mind that you will probably leave the project at some point and that other people will read your code. Undocumented huge amounts of code are worthless!)
+* Never ever use tabs
+* Indentation: JS/CSS: 2 spaces; HTML: 4 spaces
+* Don't overengineer. Don't try to solve any possible problem in one step, but try to solve problems as easy as possible and improve the solution over time!
+* Do generalize sooner or later! (if an old solution, quickly hacked together, poses more problems than it solves today, refactor it!)
+* Keep it compatible. Do not introduce changes to the public API, db schema or configurations too lightly. Don't make incompatible changes without good reasons!
+* If you do make changes, document them! (see below)
+
+## Branching model / git workflow
see git flow http://nvie.com/posts/a-successful-git-branching-model/
-* master, the stable. This is the branch everyone should use for production stuff
-* develop, everything that is READY to go into master at some point in time. This stuff is tested and ready to go out
-* release branches, stuff that should go into master very soon, only bugfixes go into these (see http://nvie.com/posts/a-successful-git-branching-model/ for why)
-* you can set tags in the master branch, there is no real need for release branches imho
-* The latest tag is not what is shown in github by default. Doing a clone of master should give you latest stable, not what is gonna be latest stable in a week, also, we should not be blocking new features to develop, just because we feel that we should be releasing it to master soon. This is the situation that release branches solve/handle.
-* hotfix branches, fixes for bugs in master
-* feature branches (in your own repos), these are the branches where you develop your features in. If its ready to go out, it will be merged into develop
+### `master` branch
+* the stable
+* This is the branch everyone should use for production stuff
+
+### `develop`branch
+* everything that is READY to go into master at some point in time
+* This stuff is tested and ready to go out
+
+### release branches
+* stuff that should go into master very soon
+* only bugfixes go into these (see http://nvie.com/posts/a-successful-git-branching-model/ for why)
+* we should not be blocking new features to develop, just because we feel that we should be releasing it to master soon. This is the situation that release branches solve/handle.
+
+### hotfix branches
+* fixes for bugs in master
+
+### feature branches (in your own repos)
+* these are the branches where you develop your features in
+* If its ready to go out, it will be merged into develop
Over the time we pull features from feature branches into the develop branch. Every month we pull from develop into master. Bugs in master get fixed in hotfix branches. These branches will get merged into master AND develop. There should never be commits in master that aren't in develop
diff --git a/Makefile b/Makefile
index ab720f28..4e870a45 100644
--- a/Makefile
+++ b/Makefile
@@ -1,13 +1,13 @@
doc_sources = $(wildcard doc/*/*.md) $(wildcard doc/*.md)
outdoc_files = $(addprefix out/,$(doc_sources:.md=.html))
-docassets = $(addprefix out/,$(wildcard doc/_assets/*))
+docassets = $(addprefix out/,$(wildcard doc/assets/*))
VERSION = $(shell node -e "console.log( require('./src/package.json').version )")
docs: $(outdoc_files) $(docassets)
-out/doc/_assets/%: doc/_assets/%
+out/doc/assets/%: doc/assets/%
mkdir -p $(@D)
cp $< $@
diff --git a/README.md b/README.md
index deb2ced2..baa8b13e 100644
--- a/README.md
+++ b/README.md
@@ -27,13 +27,13 @@ documented codebase makes it easier for developers to improve the code and contr
-Etherpad Lite is designed to be easily embeddable and provides a [HTTP API](https://github.com/Pita/etherpad-lite/wiki/HTTP-API)
-that allows your web application to manage pads, users and groups. It is recommended to use the client implementations available for this API, listed on [this wiki page](https://github.com/Pita/etherpad-lite/wiki/HTTP-API-client-libraries).
+Etherpad Lite is designed to be easily embeddable and provides a [HTTP API](https://github.com/ether/etherpad-lite/wiki/HTTP-API)
+that allows your web application to manage pads, users and groups. It is recommended to use the client implementations available for this API, listed on [this wiki page](https://github.com/ether/etherpad-lite/wiki/HTTP-API-client-libraries).
There is also a [jQuery plugin](https://github.com/johnyma22/etherpad-lite-jquery-plugin) that helps you to embed Pads into your website
**Visit [beta.etherpad.org](http://beta.etherpad.org) to test it live**
-Also, check out the **[FAQ](https://github.com/Pita/etherpad-lite/wiki/FAQ)**, really!
+Also, check out the **[FAQ](https://github.com/ether/etherpad-lite/wiki/FAQ)**, really!
# Installation
@@ -42,7 +42,7 @@ Also, check out the **[FAQ](https://github.com/Pita/etherpad-lite/wiki/FAQ)**, r
### Prebuilt windows package
This package works out of the box on any windows machine, but it's not very useful for developing purposes...
-1. Download the windows package
+1. Download the windows package
2. Extract the folder
Now, run `start.bat` and open in your browser. You like it? [Next steps](#next-steps).
@@ -51,8 +51,8 @@ Now, run `start.bat` and open in your browser. You like
You'll need [node.js](http://nodejs.org) and (optionally, though recommended) git.
1. Grab the source, either
- - download
- - or `git clone https://github.com/Pita/etherpad-lite.git` (for this you need git, obviously)
+ - download
+ - or `git clone https://github.com/ether/etherpad-lite.git` (for this you need git, obviously)
2. start `bin\installOnWindows.bat`
Now, run `start.bat` and open in your browser.
@@ -70,7 +70,7 @@ Additionally, you'll need [node.js](http://nodejs.org).
**As any user (we recommend creating a separate user called etherpad-lite):**
-1. Move to a folder where you want to install Etherpad Lite. Clone the git repository `git clone git://github.com/Pita/etherpad-lite.git`
+1. Move to a folder where you want to install Etherpad Lite. Clone the git repository `git clone git://github.com/ether/etherpad-lite.git`
2. Change into the new directory containing the cloned source code `cd etherpad-lite`
Now, run `bin\run.sh` and open in your browser.
@@ -87,7 +87,7 @@ You can modify the settings in `settings.json`. (If you need to handle multiple
You should use a dedicated database such as "mysql", if you are planning on using etherpad-lite in a production environment, since the "dirtyDB" database driver is only for testing and/or development purposes.
## Helpful resources
-The [wiki](https://github.com/Pita/etherpad-lite/wiki) is your one-stop resource for Tutorials and How-to's, really check it out! Also, feel free to improve these wiki pages.
+The [wiki](https://github.com/ether/etherpad-lite/wiki) is your one-stop resource for Tutorials and How-to's, really check it out! Also, feel free to improve these wiki pages.
Documentation can be found in `docs/`.
@@ -100,27 +100,27 @@ If you're new to node.js, start with Ryan Dahl's [Introduction to Node.js](http:
You can debug Etherpad lite using `bin/debugRun.sh`.
-If you want to find out how Etherpad's `Easysync` works (the library that makes it really realtime), start with this [PDF](https://github.com/Pita/etherpad-lite/raw/master/doc/easysync/easysync-full-description.pdf) (complex, but worth reading).
+If you want to find out how Etherpad's `Easysync` works (the library that makes it really realtime), start with this [PDF](https://github.com/ether/etherpad-lite/raw/master/doc/easysync/easysync-full-description.pdf) (complex, but worth reading).
## Getting started
You know all this and just want to know how you can help?
-Look at the [TODO list](https://github.com/Pita/etherpad-lite/wiki/TODO) and our [Issue tracker](https://github.com/Pita/etherpad-lite/issues). (Please consider using [jshint](http://www.jshint.com/about/), if you plan to contribute code.)
+Look at the [TODO list](https://github.com/ether/etherpad-lite/wiki/TODO) and our [Issue tracker](https://github.com/ether/etherpad-lite/issues). (Please consider using [jshint](http://www.jshint.com/about/), if you plan to contribute code.)
-Also, and most importantly, read our [**Developer Guidelines**](https://github.com/Pita/etherpad-lite/wiki/Developer-Guidelines), really!
+Also, and most importantly, read our [**Developer Guidelines**](https://github.com/ether/etherpad-lite/wiki/Developer-Guidelines), really!
# Get in touch
Join the [mailinglist](http://groups.google.com/group/etherpad-lite-dev) and make some noise on our freenode irc channel [#etherpad-lite-dev](http://webchat.freenode.net?channels=#etherpad-lite-dev)!
# Modules created for this project
-* [ueberDB](https://github.com/Pita/ueberDB) "transforms every database into a object key value store" - manages all database access
-* [channels](https://github.com/Pita/channels) "Event channels in node.js" - ensures that ueberDB operations are atomic and in series for each key
-* [async-stacktrace](https://github.com/Pita/async-stacktrace) "Improves node.js stacktraces and makes it easier to handle errors"
+* [ueberDB](https://github.com/ether/ueberDB) "transforms every database into a object key value store" - manages all database access
+* [channels](https://github.com/ether/channels) "Event channels in node.js" - ensures that ueberDB operations are atomic and in series for each key
+* [async-stacktrace](https://github.com/ether/async-stacktrace) "Improves node.js stacktraces and makes it easier to handle errors"
# Donate!
* [Flattr] (http://flattr.com/thing/71378/Etherpad-Foundation)
* Paypal - Press the donate button on [etherpad.org](http://etherpad.org)
# License
-[Apache License v2](http://www.apache.org/licenses/LICENSE-2.0.html)
\ No newline at end of file
+[Apache License v2](http://www.apache.org/licenses/LICENSE-2.0.html)
diff --git a/available_plugins/ep_fintest/.npmignore b/available_plugins/ep_fintest/.npmignore
deleted file mode 100644
index 74bd365b..00000000
--- a/available_plugins/ep_fintest/.npmignore
+++ /dev/null
@@ -1,7 +0,0 @@
-.git*
-docs/
-examples/
-support/
-test/
-testing.js
-.DS_Store
diff --git a/available_plugins/ep_fintest/ep.json b/available_plugins/ep_fintest/ep.json
deleted file mode 100644
index 4ec8e392..00000000
--- a/available_plugins/ep_fintest/ep.json
+++ /dev/null
@@ -1,36 +0,0 @@
-{
- "parts": [
- {
- "name": "somepart",
- "pre": [],
- "post": ["ep_onemoreplugin/partone"]
- },
- {
- "name": "partlast",
- "pre": ["ep_fintest/otherpart"],
- "post": [],
- "hooks": {
- "somehookname": "ep_fintest/partlast:somehook"
- }
- },
- {
- "name": "partfirst",
- "pre": [],
- "post": ["ep_onemoreplugin/somepart"]
- },
- {
- "name": "otherpart",
- "pre": ["ep_fintest/somepart", "ep_otherplugin/main"],
- "post": [],
- "hooks": {
- "somehookname": "ep_fintest/otherpart:somehook",
- "morehook": "ep_fintest/otherpart:morehook",
- "expressCreateServer": "ep_fintest/otherpart:expressServer",
- "eejsBlock_editbarMenuLeft": "ep_fintest/otherpart:eejsBlock_editbarMenuLeft"
- },
- "client_hooks": {
- "somehookname": "ep_fintest/static/js/test:bar"
- }
- }
- ]
-}
diff --git a/available_plugins/ep_fintest/otherpart.js b/available_plugins/ep_fintest/otherpart.js
deleted file mode 100644
index 718fb095..00000000
--- a/available_plugins/ep_fintest/otherpart.js
+++ /dev/null
@@ -1,25 +0,0 @@
-test = require("ep_fintest/static/js/test.js");
-console.log("FOOO:", test.foo);
-
-exports.somehook = function (hook_name, args, cb) {
- return cb(["otherpart:somehook was here"]);
-}
-
-exports.morehook = function (hook_name, args, cb) {
- return cb(["otherpart:morehook was here"]);
-}
-
-exports.expressServer = function (hook_name, args, cb) {
- args.app.get('/otherpart', function(req, res) {
- res.send("Abra cadabra");
- });
-}
-
-exports.eejsBlock_editbarMenuLeft = function (hook_name, args, cb) {
- args.content = args.content + '\
-
', url, escape(suite.title));
+
+ // container
+ stack[0].appendChild(el);
+ stack.unshift(document.createElement('ul'));
+ el.appendChild(stack[0]);
+ });
+
+ runner.on('suite end', function(suite){
+ if (suite.root) return;
+ stack.shift();
+ });
+
+ runner.on('fail', function(test, err){
+ if ('hook' == test.type || err.uncaught) runner.emit('test end', test);
+ });
+
+ runner.on('test end', function(test){
+ window.scrollTo(0, document.body.scrollHeight);
+
+ // TODO: add to stats
+ var percent = stats.tests / total * 100 | 0;
+ if (progress) progress.update(percent).draw(ctx);
+
+ // update stats
+ var ms = new Date - stats.start;
+ text(passes, stats.passes);
+ text(failures, stats.failures);
+ text(duration, (ms / 1000).toFixed(2));
+
+ // test
+ if ('passed' == test.state) {
+ var el = fragment('
%e%ems
', test.speed, test.title, test.duration);
+ } else if (test.pending) {
+ var el = fragment('
%e
', test.title);
+ } else {
+ var el = fragment('
%e
', test.title);
+ var str = test.err.stack || test.err.toString();
+
+ // FF / Opera do not add the message
+ if (!~str.indexOf(test.err.message)) {
+ str = test.err.message + '\n' + str;
+ }
+
+ // <=IE7 stringifies to [Object Error]. Since it can be overloaded, we
+ // check for the result of the stringifying.
+ if ('[object Error]' == str) str = test.err.message;
+
+ // Safari doesn't give you a stack. Let's at least provide a source line.
+ if (!test.err.stack && test.err.sourceURL && test.err.line !== undefined) {
+ str += "\n(" + test.err.sourceURL + ":" + test.err.line + ")";
+ }
+
+ el.appendChild(fragment('