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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -181,7 +181,7 @@ Accessed via the info icon in the title bar. This view contains tabs for reading
181
181
The **General** settings category includes a **PlantUML Rendering** selector. Choose between:
182
182
183
183
-**Remote (plantuml.com):** Encodes the diagram and requests the SVG from the public PlantUML server.
184
-
-**Offline (local renderer):** Invokes the bundled PlantUML engine inside the desktop application. This mode requires a local Java Runtime Environment and access to Graphviz (or the bundled `viz.js` assets) so the renderer can generate diagrams without contacting plantuml.com.
184
+
-**Offline (local renderer):** Invokes the PlantUML jar bundled with the application (`assets/plantuml/plantuml.jar`) through the local Java Runtime Environment, letting the app render diagrams without contacting plantuml.com.
185
185
186
186
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.
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
@@ -14,7 +14,7 @@ This document provides a technical overview of the DocForge application's archit
14
14
-**Bundler:**[esbuild](https://esbuild.github.io/) for fast and efficient bundling of the application's source code.
15
15
-**Styling:**[Tailwind CSS](https://tailwindcss.com/) for a utility-first CSS framework.
16
16
-**Packaging:**[electron-builder](https://www.electron.build/) for creating distributable application packages.
17
-
-**Diagram Rendering:**[PlantUML](https://plantuml.com/) via either the public plantuml.com service or the bundled [`node-plantuml`](https://www.npmjs.com/package/node-plantuml) renderer. Offline rendering requires a locally installed Java Runtime Environment and access to Graphviz (or the cached `viz.js` binary) so that diagrams can be rendered without network access.
17
+
-**Diagram Rendering:**[PlantUML](https://plantuml.com/) via either the public plantuml.com service or a PlantUML jar bundled with the application (`assets/plantuml/plantuml.jar`). Offline rendering invokes the jar through the system Java Runtime Environment, so diagrams render without any network connectivity.
18
18
19
19
---
20
20
@@ -95,7 +95,7 @@ This system provides a consistent and extensible editing experience for all docu
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
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.
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 Java-based IPC bridge depending on the active setting.
Copy file name to clipboardExpand all lines: docs/FUNCTIONAL_MANUAL.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -181,7 +181,7 @@ Accessed via the info icon in the title bar. This view contains tabs for reading
181
181
The **General** settings category includes a **PlantUML Rendering** selector. Choose between:
182
182
183
183
-**Remote (plantuml.com):** Encodes the diagram and requests the SVG from the public PlantUML server.
184
-
-**Offline (local renderer):** Invokes the bundled PlantUML engine inside the desktop application. This mode requires a local Java Runtime Environment and access to Graphviz (or the bundled `viz.js` assets) so the renderer can generate diagrams without contacting plantuml.com.
184
+
-**Offline (local renderer):** Invokes the PlantUML jar bundled with the application (`assets/plantuml/plantuml.jar`) through the local Java Runtime Environment, letting the app render diagrams without contacting plantuml.com.
185
185
186
186
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.
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
@@ -14,7 +14,7 @@ This document provides a technical overview of the DocForge application's archit
14
14
-**Bundler:**[esbuild](https://esbuild.github.io/) for fast and efficient bundling of the application's source code.
15
15
-**Styling:**[Tailwind CSS](https://tailwindcss.com/) for a utility-first CSS framework.
16
16
-**Packaging:**[electron-builder](https://www.electron.build/) for creating distributable application packages.
17
-
-**Diagram Rendering:**[PlantUML](https://plantuml.com/) via either the public plantuml.com service or the bundled [`node-plantuml`](https://www.npmjs.com/package/node-plantuml) renderer. Offline rendering requires a locally installed Java Runtime Environment and access to Graphviz (or the cached `viz.js` binary) so that diagrams can be rendered without network access.
17
+
-**Diagram Rendering:**[PlantUML](https://plantuml.com/) via either the public plantuml.com service or a PlantUML jar bundled with the application (`assets/plantuml/plantuml.jar`). Offline rendering invokes the jar through the system Java Runtime Environment, so diagrams render without any network connectivity.
18
18
19
19
---
20
20
@@ -95,7 +95,7 @@ This system provides a consistent and extensible editing experience for all docu
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
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.
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 Java-based IPC bridge depending on the active setting.
0 commit comments