Lines Matching refs:in

9 If you install this plugin manually, make sure it is installed in
14 on how to install plugins in DokuWiki.
43   - `renderer.php` uses the classes `NodeStack` `Node` and `Mark` in `schema` to do its job
45   - to keep information about a Node in as few places as possible,
47 - Prosemirror parses that json in `script/main.js` according to the schema defined in
51 - Some Nodes (e.g. images, links) need to be resolved by DokuWiki in order to be rendered properly.
53   - triggered by `LinkForm.resolveSubmittedLinkData` in `script/LinkForm.js`
59 - Prosemirror synchronizes all changes with the underlying json in the `<input>` field
61 - This starts in `action/parser.php` during the event `ACTION_ACT_PREPROCESS`
63   - This means that the Syntax `**bold __underlined and bold__**` is represented in Prosemirror's data as
65   - The creation of that syntax tree is started in `parser/SyntaxTreeBuilder.php`
67     - To know in which order we have to open/close marks we need to know which start
73     - If the marks on a node have the same start/end than they need a stable order in which they appear.
74     That is defined in `Mark::markOrder`
77 Currently all our prosemirror scripts are in `script/`.
86 - possibly `commands` in general wich then can be used by menu-items and keyboard-events?
94 in `_test/json/`. This data is used for three sets of tests:
95 1. Testing the rendering of DokuWiki-Syntax to Prosemirror JSON in `_test/renderer.test.php`
96 1. Testing the parsing of Prosemirror JSON back to the original DokuWiki-Syntax in `_test/jsonParser.test.php`
97 1. Testing the validity of the Prosemirror JSON against the schema (`script/schema.js`) in `_jstest/test.js`
102 The scripts in `script/` are also checked when building with eslint.
115 This program is distributed in the hope that it will be useful,
120 See the COPYING file in your DokuWiki folder for details