Quick start, manual, FAQ, tips: wires are dragged from a terminal, double-click placing, Edit submenus, autosave off by default
Screenshots for script buttons, live mode, macro recorder and the merged features documented today (from the PRs' own captures; recovery-dialog path masked)
Document merged features that had no wiki coverage
Symbol editor background frame (#1164); configuration files and remembered
dialog sizes (#1166, #1165); ranked-list search option (#1083); crash-recovery
copies and crash reports in the FAQ (#1167, #1013, #1031, #1181); double-click
wire colour and one-text-per-sheet applying at once (#1172, #1191); cabinet
thumbnails (#1170); linked copies on paste/duplicate (#997); second click in a
group (#1110); align icons (#1153); uuid lookups for sheets, tables and symbol
texts (#1098, #1114); database filled from the document (#1142); value
suggestions and text-width handles (#1021, #591).
Call a folio a sheet, as the English interface now does (PR #1216)
Prose only: page URLs (folio_links, navigating_folios), image names, code,
XML tag and variable names, and French menu names are unchanged. Readers
arriving from older forum posts are told a sheet used to be called a folio.
Generated by qelectrotech-docker tools/wiki-folio-sheet/rename.py.
Document DXF: two unrelated features reduced to one bullet each
sources/createdxf.*, sources/dxfpaintdevice.*, sources/dxf/dxftoelmt.*
total ~1,780 lines. The only wiki coverage was a single repeated bullet
-- 'DXF -- CAD format for collaboration' -- across features, faq and
user_manual, in all three languages, describing neither direction
accurately: it reads as one feature, and it's actually two that share
nothing but a file extension.
Export (File -> Export, alongside PDF/PNG/SVG, in-process) reuses every
item's existing paint() code through a custom QPaintEngine
(DxfPaintEngine) rather than a separate DXF renderer -- documented from
that class's own thorough header comment, including the real fidelity
table it specifies: rectangles and filled paths lose their fill (no
HATCH primitive in this DXF dialect), arcs become straight-line chords,
and images become position-preserving placeholder rectangles since DXF
has no raster entity here. No CLI verb exists for it, unlike PDF/PNG/SVG.
Import (element editor only, not the diagram editor -- File -> Import a
DXF file) is a symbol-authoring tool: it shells out to dxf2elmt, a
separate third-party program QET does not bundle, the same external-tool
pattern as qet_tb_generator already documented in api_reference. Traces
the actual call: , stdout read as .elmt XML, pushed
onto the element editor's undo stack as one operation.
Makes explicit what neither direction is: not a way to place a DXF
drawing on a folio, not round-trip safe (export's own limitations rule
that out before even considering the code is entirely separate), and not
a full CAD interchange path -- no layers, blocks or metadata, just
primitives.
Links the existing one-line mentions in features/faq/user_manual (all
three languages) to the new page instead of rewriting them, since they
are fine as list bullets. EN/FR/DE.
Correct the automation docs: QET has no Python scripting and no plugins
api_reference stated "QElectroTech supports Python scripting" and
"QElectroTech supports plugins for deep integration", and told readers to
install plugins into ~/.local/share/QElectroTech/plugins/ and platform
equivalents. None of it exists: there is no QPluginLoader anywhere in
sources/, no plugin ABI, and every Python reference in the tree is the
launcher for qet_tb_generator -- a separate PyPI program QET starts as an
ordinary child process. QET never reads those plugin paths.
cli_reference had the mirror-image error, calling the shipped headless
export "Future CLI Features (QET 2.0)" and sending readers to the
scripting that does not exist. The FR/DE CLI pages additionally invented
a --dpi option and QET_PLUGIN_PATH / QET_ELEMENT_PATH, and documented an
argument order the parser cannot accept.
Rewrites api_reference (EN/FR/DE) around what is actually there: the 13
CLI verbs with their real positional syntax and exit codes, the real .qet
and .elmt XML (the old skeletons were invented -- no <diagrams> wrapper,
element has no id, uuid is an attribute), qet_tb_generator, and the C++
source. Adds a section naming what does not exist, so the claim does not
come back.
Also corrects the same claims where they had spread: features, history,
faq, user_manual (EN/FR/DE) and the sidebar.
Complete Tier 1: Quick Start Guide, User Manual, and FAQ
Quick Start Guide (10-minute onboarding):
- Platform-specific installation (Windows, macOS, Linux)
- Step-by-step project creation and first diagram
- Interface overview and toolbar guide
- Adding elements and drawing wires
- Labeling and saving
- Common first-time tasks and shortcuts
User Manual (comprehensive reference):
- Basics and interface overview with diagram
- Projects and folios (pages/diagrams)
- Working with elements (find, place, select, move, rotate)
- Drawing and editing wires/conductors
- Text, labels, and dynamic fields
- Editing, alignment, zoom, snap-to-grid
- Reports, export, and printing
- Preferences and settings
- Keyboard shortcuts table
- Troubleshooting section
- Links to advanced topics
FAQ (60+ questions with practical answers):
- Installation and setup for all platforms
- Getting started with projects and diagrams
- Common beginner questions about elements, wires, labels
- Creating and saving projects
- Organization and sharing
- Performance and troubleshooting
- File compatibility and advanced topics
- Platform-specific guidance
- Active community support pointers
Research gathered from:
- qelectrotech.org official manual structure
- GitHub releases and documentation
- Forum activity analysis
- Official example projects
- Official element collections
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GtMZqGEiUMvDBqcFvVG2vb
Redesign wiki home page for end-users; add structure and stub pages
- Reorganize Home.md with end-user-first structure
- Add Getting Started, User Documentation, Development sections
- Create stub pages for Quick Start Guide, User Manual, FAQ, Tips & Tricks
- Add developer stubs: Building, Contributing, Development Roadmap
- Add About section: History, Features, License, Community
The stubs provide structure and placeholders ready for content to be filled in.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GtMZqGEiUMvDBqcFvVG2vb