Align wiki pages with the implementation on master
Checked the setup, GUI, tool widget, and core API pages against the
source code and corrected everything that did not match, including:
- Building HAL: the GUI requires Qt6 (not Qt5); Ubuntu 26.04; bundled
ABC already patched; plugins load immediately in the Plugin Manager.
- Using HAL: File > Import … / Export … submenus and preconditions,
autosave and crash recovery, project directory layout.
- Plugin Manager, Logic Evaluator: both are part of master; correct
menu paths, launch paths, build options, and truth table limits.
- Graph View, Views, Modules, Selection Details, Groupings, Log,
Python Editor/Console: exact context menu labels, removing items
from views, automatic deletion of empty views, navigation colors,
shared Python namespace, scripts saved with the project.
- Core API: get_resolved_boolean_function flag semantics, subgraph
decorator fails on flip-flops, broken snippets (Add, connect_gates,
GateLibrary), net/ID details, missing properties, broken links.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Give every page a See also section and fix the broken links
The wiki used three different headings for the same thing — See also,
Where to go from here, and Related. Settle on See also everywhere, except
for the five example projects, which keep Where to go from here because
their closing sections are next steps rather than pointers.
Add the section to the 45 pages that had none, including the stubs, where
it at least gives the reader somewhere to go. Point the three broken links
at the sections they were meant to reference: user interactions in GUI.md
and neighborhoods in Graph-Algorithms.md both exist on the page itself.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Align header style and refine the introduction and example pages
Headers:
- Convert all page headers to sentence case, preserving acronyms, proper
nouns, and code identifiers. GitHub derives anchors by lowercasing, so
existing #anchor links are unaffected.
Introduction to HAL:
- Link "plugins" to the plugin index
- Correct the claim about the university lecture: HAL underpins its
practical part, and the example projects overlap only part of it
- Describe recovering high-level structure as several complementary
steps rather than one dominant one
- Move "publish reproducible research" to the end of the applications
Using HAL:
- Introduce the top module before referring to it, and move its snippet
into the Python section so no code precedes the Python introduction
- Rewrite the Python examples for readers new to Python, pull the IDs
section to the front, and give every item the same paragraph form
- Explain that the gate library and Python scripts may live outside the
project directory, and that an export always collects them
- Turn the netlist import dialog fields into an enumerated list
- Correct why a recovered netlist has no hierarchy: it is a design-time
construct absent from the chip or bitstream, not something synthesis
necessarily removes
Example projects:
- List each project once instead of three times
- Replace the empty-header tables with definition lists
Crypto Trojan and HAWKEYE:
- Document the ready-to-run hawkeye.py, the preprocessing it needs, and
the S-box database now shipped with HAL
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated graph view and widgets
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Updated Python Editor Widget (markdown)
Created Python Editor Widget (markdown)