You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: FUNCTIONAL_MANUAL.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,6 +150,8 @@ The **General** settings category includes a **PlantUML Rendering** selector. Ch
150
150
151
151
If the Java runtime is unavailable, DocForge will report the error in the preview and you can switch back to remote rendering at any time.
152
152
153
+
The chosen rendering mode is used for PlantUML code blocks inside Markdown documents *and* for standalone `.puml` documents rendered through the dedicated PlantUML previewer.
154
+
153
155
### Logger Panel
154
156
155
157
Accessed via the terminal icon in the title bar, this panel is your primary tool for debugging and monitoring application activity.
Copy file name to clipboardExpand all lines: TECHNICAL_MANUAL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,8 +94,8 @@ This system provides a consistent and extensible editing experience for all docu
94
94
-**`CodeEditor.tsx`:** A React component that wraps and configures the Monaco Editor instance. It's responsible for managing the editor's content, theme, and language for syntax highlighting based on props.
95
95
-**`PreviewPane.tsx`:** This component is responsible for displaying the rendered output of a document. It debounces content updates for performance and uses the `PreviewService` to get the correct output.
96
96
-**`services/previewService.ts`:** This service acts as a registry for all available renderer "plugins." It exposes a method, `getRendererForLanguage()`, which finds and returns the appropriate renderer for a given language ID (e.g., 'markdown').
97
-
-**Renderer Plugins (`services/preview/`):** Each file format with a preview is supported by a dedicated renderer class that implements the `IRenderer` interface. This makes the system highly extensible: to support a new format, one only needs to create a new renderer class and add it to the `previewService` registry. Currently, renderers for Markdown, HTML, and plaintext (fallback) are implemented.
98
-
-The Markdown renderer now integrates an offline PlantUML path. When users select the offline mode, the renderer invokes the main-process`node-plantuml` bridge to generate SVG output locally; otherwise it falls back to the remote plantuml.com service.
97
+
-**Renderer Plugins (`services/preview/`):** Each file format with a preview is supported by a dedicated renderer class that implements the `IRenderer` interface. This makes the system highly extensible: to support a new format, one only needs to create a new renderer class and add it to the `previewService` registry. The bundled plugins cover Markdown (with Mermaid + PlantUML support), standalone PlantUML documents, HTML, PDFs, common image formats, and a plaintext fallback renderer.
98
+
-Both the Markdown renderer and the standalone PlantUML renderer share the `PlantUMLDiagram` component, which routes diagrams through either the remote plantuml.com server or the offline`node-plantuml`IPC bridge depending on the active setting.
Copy file name to clipboardExpand all lines: docs/FUNCTIONAL_MANUAL.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,6 +150,8 @@ The **General** settings category includes a **PlantUML Rendering** selector. Ch
150
150
151
151
If the Java runtime is unavailable, DocForge will report the error in the preview and you can switch back to remote rendering at any time.
152
152
153
+
The chosen rendering mode is used for PlantUML code blocks inside Markdown documents *and* for standalone `.puml` documents rendered through the dedicated PlantUML previewer.
154
+
153
155
### Logger Panel
154
156
155
157
Accessed via the terminal icon in the title bar, this panel is your primary tool for debugging and monitoring application activity.
Copy file name to clipboardExpand all lines: docs/TECHNICAL_MANUAL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,8 +94,8 @@ This system provides a consistent and extensible editing experience for all docu
94
94
-**`CodeEditor.tsx`:** A React component that wraps and configures the Monaco Editor instance. It's responsible for managing the editor's content, theme, and language for syntax highlighting based on props.
95
95
-**`PreviewPane.tsx`:** This component is responsible for displaying the rendered output of a document. It debounces content updates for performance and uses the `PreviewService` to get the correct output.
96
96
-**`services/previewService.ts`:** This service acts as a registry for all available renderer "plugins." It exposes a method, `getRendererForLanguage()`, which finds and returns the appropriate renderer for a given language ID (e.g., 'markdown').
97
-
-**Renderer Plugins (`services/preview/`):** Each file format with a preview is supported by a dedicated renderer class that implements the `IRenderer` interface. This makes the system highly extensible: to support a new format, one only needs to create a new renderer class and add it to the `previewService` registry. Currently, renderers for Markdown, HTML, and plaintext (fallback) are implemented.
98
-
-The Markdown renderer now integrates an offline PlantUML path. When users select the offline mode, the renderer invokes the main-process`node-plantuml` bridge to generate SVG output locally; otherwise it falls back to the remote plantuml.com service.
97
+
-**Renderer Plugins (`services/preview/`):** Each file format with a preview is supported by a dedicated renderer class that implements the `IRenderer` interface. This makes the system highly extensible: to support a new format, one only needs to create a new renderer class and add it to the `previewService` registry. The bundled plugins cover Markdown (with Mermaid + PlantUML support), standalone PlantUML documents, HTML, PDFs, common image formats, and a plaintext fallback renderer.
98
+
-Both the Markdown renderer and the standalone PlantUML renderer share the `PlantUMLDiagram` component, which routes diagrams through either the remote plantuml.com server or the offline`node-plantuml`IPC bridge depending on the active setting.
0 commit comments