Fossil SCM
Tiny pikchr-internal doc updates. No functional changes.
Commit
44e1c41986c43ebee83ae630590d5786f746a1bffebc03b1d3cdf83a1a51cbf5
Parent
7d28ae44fe56e99…
2 files changed
+4
-4
+1
-1
+4
-4
| --- extsrc/pikchr-worker.js | ||
| +++ extsrc/pikchr-worker.js | ||
| @@ -36,11 +36,11 @@ | ||
| 36 | 36 | pikchr: source code for the pikchr, |
| 37 | 37 | darkMode: boolean true to adjust colors for a dark color scheme, |
| 38 | 38 | cssClass: CSS class name to add to the SVG |
| 39 | 39 | } |
| 40 | 40 | |
| 41 | - Workers-to-Main types | |
| 41 | + Workers-to-Main message types: | |
| 42 | 42 | |
| 43 | 43 | - stdout, stderr: indicate stdout/stderr output from the wasm |
| 44 | 44 | layer. The data property is the string of the output, noting |
| 45 | 45 | that the emscripten binding emits these one line at a time. Thus, |
| 46 | 46 | if a C-side puts() emits multiple lines in a single call, the JS |
| @@ -50,21 +50,21 @@ | ||
| 50 | 50 | |
| 51 | 51 | - module: Status text. This is intended to alert the main thread |
| 52 | 52 | about module loading status so that, e.g., the main thread can |
| 53 | 53 | update a progress widget and DTRT when the module is finished |
| 54 | 54 | loading and available for work. Status messages come in the form |
| 55 | - | |
| 55 | + | |
| 56 | 56 | {type:'module', data:{ |
| 57 | 57 | type:'status', |
| 58 | 58 | data: {text:string|null, step:1-based-integer} |
| 59 | 59 | } |
| 60 | 60 | |
| 61 | 61 | with an incrementing step value for each subsequent message. When |
| 62 | 62 | the module loading is complete, a message with a text value of |
| 63 | 63 | null is posted. |
| 64 | 64 | |
| 65 | - - pikchr: | |
| 65 | + - pikchr: | |
| 66 | 66 | |
| 67 | 67 | {type: 'pikchr', |
| 68 | 68 | data:{ |
| 69 | 69 | pikchr: input text, |
| 70 | 70 | result: rendered result (SVG on success, HTML on error), |
| @@ -162,11 +162,11 @@ | ||
| 162 | 162 | } |
| 163 | 163 | return; |
| 164 | 164 | }; |
| 165 | 165 | console.warn("Unknown pikchr-worker message type:",ev); |
| 166 | 166 | }; |
| 167 | - | |
| 167 | + | |
| 168 | 168 | /** |
| 169 | 169 | emscripten module for use with build mode -sMODULARIZE. |
| 170 | 170 | */ |
| 171 | 171 | const pikchrModule = { |
| 172 | 172 | print: function(){wMsg('stdout', Array.prototype.slice.call(arguments));}, |
| 173 | 173 |
| --- extsrc/pikchr-worker.js | |
| +++ extsrc/pikchr-worker.js | |
| @@ -36,11 +36,11 @@ | |
| 36 | pikchr: source code for the pikchr, |
| 37 | darkMode: boolean true to adjust colors for a dark color scheme, |
| 38 | cssClass: CSS class name to add to the SVG |
| 39 | } |
| 40 | |
| 41 | Workers-to-Main types |
| 42 | |
| 43 | - stdout, stderr: indicate stdout/stderr output from the wasm |
| 44 | layer. The data property is the string of the output, noting |
| 45 | that the emscripten binding emits these one line at a time. Thus, |
| 46 | if a C-side puts() emits multiple lines in a single call, the JS |
| @@ -50,21 +50,21 @@ | |
| 50 | |
| 51 | - module: Status text. This is intended to alert the main thread |
| 52 | about module loading status so that, e.g., the main thread can |
| 53 | update a progress widget and DTRT when the module is finished |
| 54 | loading and available for work. Status messages come in the form |
| 55 | |
| 56 | {type:'module', data:{ |
| 57 | type:'status', |
| 58 | data: {text:string|null, step:1-based-integer} |
| 59 | } |
| 60 | |
| 61 | with an incrementing step value for each subsequent message. When |
| 62 | the module loading is complete, a message with a text value of |
| 63 | null is posted. |
| 64 | |
| 65 | - pikchr: |
| 66 | |
| 67 | {type: 'pikchr', |
| 68 | data:{ |
| 69 | pikchr: input text, |
| 70 | result: rendered result (SVG on success, HTML on error), |
| @@ -162,11 +162,11 @@ | |
| 162 | } |
| 163 | return; |
| 164 | }; |
| 165 | console.warn("Unknown pikchr-worker message type:",ev); |
| 166 | }; |
| 167 | |
| 168 | /** |
| 169 | emscripten module for use with build mode -sMODULARIZE. |
| 170 | */ |
| 171 | const pikchrModule = { |
| 172 | print: function(){wMsg('stdout', Array.prototype.slice.call(arguments));}, |
| 173 |
| --- extsrc/pikchr-worker.js | |
| +++ extsrc/pikchr-worker.js | |
| @@ -36,11 +36,11 @@ | |
| 36 | pikchr: source code for the pikchr, |
| 37 | darkMode: boolean true to adjust colors for a dark color scheme, |
| 38 | cssClass: CSS class name to add to the SVG |
| 39 | } |
| 40 | |
| 41 | Workers-to-Main message types: |
| 42 | |
| 43 | - stdout, stderr: indicate stdout/stderr output from the wasm |
| 44 | layer. The data property is the string of the output, noting |
| 45 | that the emscripten binding emits these one line at a time. Thus, |
| 46 | if a C-side puts() emits multiple lines in a single call, the JS |
| @@ -50,21 +50,21 @@ | |
| 50 | |
| 51 | - module: Status text. This is intended to alert the main thread |
| 52 | about module loading status so that, e.g., the main thread can |
| 53 | update a progress widget and DTRT when the module is finished |
| 54 | loading and available for work. Status messages come in the form |
| 55 | |
| 56 | {type:'module', data:{ |
| 57 | type:'status', |
| 58 | data: {text:string|null, step:1-based-integer} |
| 59 | } |
| 60 | |
| 61 | with an incrementing step value for each subsequent message. When |
| 62 | the module loading is complete, a message with a text value of |
| 63 | null is posted. |
| 64 | |
| 65 | - pikchr: |
| 66 | |
| 67 | {type: 'pikchr', |
| 68 | data:{ |
| 69 | pikchr: input text, |
| 70 | result: rendered result (SVG on success, HTML on error), |
| @@ -162,11 +162,11 @@ | |
| 162 | } |
| 163 | return; |
| 164 | }; |
| 165 | console.warn("Unknown pikchr-worker message type:",ev); |
| 166 | }; |
| 167 | |
| 168 | /** |
| 169 | emscripten module for use with build mode -sMODULARIZE. |
| 170 | */ |
| 171 | const pikchrModule = { |
| 172 | print: function(){wMsg('stdout', Array.prototype.slice.call(arguments));}, |
| 173 |
+1
-1
| --- src/fossil.page.pikchrshowasm.js | ||
| +++ src/fossil.page.pikchrshowasm.js | ||
| @@ -524,11 +524,11 @@ | ||
| 524 | 524 | ForceResizeKludge(); |
| 525 | 525 | }/*onPikchrshowLoaded()*/; |
| 526 | 526 | |
| 527 | 527 | |
| 528 | 528 | /** |
| 529 | - Predefined scripts. Each entry is an object: | |
| 529 | + Predefined example pikchr scripts. Each entry is an object: | |
| 530 | 530 | |
| 531 | 531 | { |
| 532 | 532 | name: required string, |
| 533 | 533 | code: optional code string. An entry with a falsy code is treated |
| 534 | 534 | like a separator in the resulting SELECT element (a |
| 535 | 535 |
| --- src/fossil.page.pikchrshowasm.js | |
| +++ src/fossil.page.pikchrshowasm.js | |
| @@ -524,11 +524,11 @@ | |
| 524 | ForceResizeKludge(); |
| 525 | }/*onPikchrshowLoaded()*/; |
| 526 | |
| 527 | |
| 528 | /** |
| 529 | Predefined scripts. Each entry is an object: |
| 530 | |
| 531 | { |
| 532 | name: required string, |
| 533 | code: optional code string. An entry with a falsy code is treated |
| 534 | like a separator in the resulting SELECT element (a |
| 535 |
| --- src/fossil.page.pikchrshowasm.js | |
| +++ src/fossil.page.pikchrshowasm.js | |
| @@ -524,11 +524,11 @@ | |
| 524 | ForceResizeKludge(); |
| 525 | }/*onPikchrshowLoaded()*/; |
| 526 | |
| 527 | |
| 528 | /** |
| 529 | Predefined example pikchr scripts. Each entry is an object: |
| 530 | |
| 531 | { |
| 532 | name: required string, |
| 533 | code: optional code string. An entry with a falsy code is treated |
| 534 | like a separator in the resulting SELECT element (a |
| 535 |