Skip to content

The README says what phase 2 is now #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ddehilster merged 2 commits into from
Sep 17, 2026
Merged

The README says what phase 2 is now #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef3eabf
The README says what phase 2 is now
ddehilster Sep 17, 2026
c1e3ddb
The package says both pages use it now
ddehilster Sep 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ see the parse tree — with no install, no C++ toolchain, and no VS Code.
| Phase | What | State |
|---|---|---|
| **1. Stopgap** | `openvscode-server` container with the real `dehilster.nlp` extension baked in | **in this repo** — see [stopgap/](stopgap/) |
| **2. Studio** | Purpose-built web app: Monaco front end + an API server running the engine | **started** — in [studio/](studio/): the editor, and running analyzers through a local run server |
| **Shared lists** | `@visualtext/analyzer-views`: the pass sequence and knowledge base as web components, for the studio and any other page that lists an analyzer | **in this repo** — see [analyzer-views/](analyzer-views/) |
| **2. Studio** | Purpose-built web app: Monaco front end + an API server running the engine | **live** — in [studio/](studio/): the editor, the run server, analyzers opened from GitHub and committed back, deployed at studio.visualtext.org/studio/ for invited people |
| **Shared views** | `@visualtext/analyzer-views`: the sequence, knowledge base, output files, parse trees, code, log and values as web components, for the studio and any other page that shows an analyzer | **released** — see [analyzer-views/](analyzer-views/) |
| **3. Client-side** | Emscripten/WASM build of the engine for zero-server demos | speculative |

Phase 1 exists to have something live quickly — a "Try NLP++" button for
Expand All @@ -39,7 +39,8 @@ npm run dev # in a second terminal: http://localhost:5173
```

Edit an analyzer and press **Run** (F5) to run it on the input file. Under the editor, **Output**
lists the files it wrote, with **Problems** and **Log** beside it; the same files are listed in
shows the values the run found — the fields its `output.json` filled, by name — and lists the
files it wrote, with **Problems** and **Log** beside it; the same files are listed in
the file list under **Output**, and its parse tree under **Parse trees**, each with the icon the
VS Code extension gives it. Click one and it fills the
editor, read-only — a tree coloured as the extension colours trees, node names green, rewrites
Expand Down
9 changes: 5 additions & 4 deletions analyzer-views/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,11 @@ This package shows an NLP++ analyzer's pass sequence, knowledge base, run result
[NLP++ extension for VS Code](https://github.com/VisualText/vscode-nlp) does, on any web page.
It works with plain DOM code, React or any other framework.

It exists so that every page that lists an analyzer does it the same way. NLP Studio uses it
today, and the admin console's Browse and run is next. A rule is changed once, here: for
example, the knowledge base lists only `.dict` and `.kbb` files, never the engine's `.kb`
files.
It exists so that every page that lists an analyzer does it the same way. NLP Studio uses it,
and so does the admin console's Browse and run, which installs it from a release. A rule is
changed once, here, and both pages get it: the knowledge base lists only `.dict` and `.kbb`
files and never the engine's `.kb` files, a switched-off pass keeps the number the engine
gives it, and a `-DEV` run's per-pass trees and rule matches are read the same way in each.

## Use

Expand Down
Loading