root / webodf / README @ a0517e39
History | View | Annotate | Download (1.6 kB)
| 1 | 9f023ec4 | Jos van den Oever | This directory contains the javacript code to WebODF as well as applications that use it. The applications are browser applications, commandline applications and unit tests. |
|---|---|---|---|
| 2 | 9f023ec4 | Jos van den Oever | |
| 3 | 9f023ec4 | Jos van den Oever | lib/ |
| 4 | 9f023ec4 | Jos van den Oever | lib/core/ Parts of WebODF that also work on JavaScript runtimes without a |
| 5 | 9f023ec4 | Jos van den Oever | document window. |
| 6 | 9f023ec4 | Jos van den Oever | lib/gui/ Parts of WebODF that require a domtree |
| 7 | 9f023ec4 | Jos van den Oever | |
| 8 | 9f023ec4 | Jos van den Oever | The library should be able to run in a number of different runtimes. Currently these are: |
| 9 | 9f023ec4 | Jos van den Oever | - a webbrowser |
| 10 | 9f023ec4 | Jos van den Oever | - node.js |
| 11 | 9f023ec4 | Jos van den Oever | - rhino |
| 12 | 9f023ec4 | Jos van den Oever | A common API is implemented for these three environments in the files lib/browser.js, lib/node.js and lib/rhino.js respectively. |
| 13 | 9f023ec4 | Jos van den Oever | |
| 14 | 9f023ec4 | Jos van den Oever | |
| 15 | e486ed42 | Jos van den Oever | |
| 16 | e486ed42 | Jos van den Oever | Requirements on the code |
| 17 | e486ed42 | Jos van den Oever | |
| 18 | e486ed42 | Jos van den Oever | There are several requirements that need to met before code can be considered for inclusion in WebODF. Most requirements can be checked automatically, a few have to be checked by hand. A contribution must: |
| 19 | e486ed42 | Jos van den Oever | - be contributed under the appropriate license |
| 20 | e486ed42 | Jos van den Oever | - be javascript |
| 21 | e486ed42 | Jos van den Oever | - not give any warnings in a JSLint check |
| 22 | e486ed42 | Jos van den Oever | - be unchanged when passed through jsbeautifier |
| 23 | e486ed42 | Jos van den Oever | - compile with the closure compiler |
| 24 | e486ed42 | Jos van den Oever | - must pass all the unit tests that were passed before |
| 25 | e486ed42 | Jos van den Oever | - as separate js files in the currenlty used Node.JS implementation |
| 26 | e486ed42 | Jos van den Oever | - as a single compiled file in the currenlty used Node.JS implementation |
| 27 | e486ed42 | Jos van den Oever | - as separate js files in the currenlty used Rhino implementation |
| 28 | e486ed42 | Jos van den Oever | - as a single compiled file Rhino implementation |
| 29 | e486ed42 | Jos van den Oever | - must have equal or greater code coverage for the each of the test runs |
| 30 | c2299922 | Jos van den Oever | |
| 31 | c2299922 | Jos van den Oever | The automatic checks can be performed by running a dedicated command that reports in an xml file. This report is compared to the previous report. |
| 32 | c2299922 | Jos van den Oever | |
| 33 | c2299922 | Jos van den Oever | runtests.js is the command that creates a report. |
| 34 | c2299922 | Jos van den Oever | |
| 35 | c2299922 | Jos van den Oever | |
| 36 | c2299922 | Jos van den Oever | |
| 37 | c2299922 | Jos van den Oever | |
| 38 | c2299922 | Jos van den Oever | |
| 39 | c2299922 | Jos van den Oever | |
| 40 | c2299922 | Jos van den Oever | |
| 41 | c2299922 | Jos van den Oever | |
| 42 | c2299922 | Jos van den Oever |