Settings file, Windows long paths, interface language, 3D mouse build
New page settings_file (save/load settings, PR #1166). Windows: long
symbol paths (#1243, #1244), moving settings to another PC. Languages:
interface language, sheet vs folio (#1216, #1124, #1261), pt_BR (#1189),
phrase books (#1006). 3D mouse: correct menu path to its settings.
Building: Qt6 is the default now, and CUPS is required
Following these instructions on current master fails. Two reasons, both
verified against a clean checkout today:
- The page is Qt5-first, listing qtbase5-dev and friends with Qt6 as an
afterthought. a1c090781 made QT_VERSION_MAJOR default to 6 and retired
the Qt5 track, so the default build is Qt6.
- CUPS is not mentioned anywhere, but configuring a clean master without
the development headers fails with "Could NOT find Cups" before
anything is compiled. QET does not use CUPS itself; the build compiles
KF6CoreAddons and KF6WidgetsAddons from source by default and those
need it. Noted, with -DBUILD_KF=NO as the alternative for anyone who
would rather use their distribution's KDE Frameworks packages.
Package lists rewritten around Qt6 for Debian/Ubuntu, Fedora and Arch,
and macOS/Windows updated to lead with Qt6 rather than Qt5.
The Troubleshooting section was three placeholder lines; filled in with
the errors actually hit, including the stale ~/.cache/qet-deps that
survives deleting the build directory and then fails demanding Qt6 on a
tree previously configured for Qt5.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Complete Tier 3: Contributing, Building, and Development Roadmap
Contributing Page (developer guide):
- Technical stack: C++, Qt5/Qt6, CMake, Catch2/googletest
- Development setup with recursive clone
- Complete dev environment configuration for all platforms
- Code guidelines (formatting with clang-format, testing)
- Commit message best practices with examples
- PR submission and review process
- Table of key technologies and tools
Building Page (compilation guide):
- Platform-specific prerequisites (Linux, macOS, Windows)
- Detailed package installation instructions
- WSL option for Windows developers
- Git clone with submodules
- CMake build configuration steps
- Build variants and testing
- Troubleshooting common build issues
Development Roadmap (QET 2.0 vision):
- QET 2.0 refactoring as major initiative
- Prerequisites before refactoring begins (terminal strip gen, etc)
- Four phases of architectural changes:
* File format modernization (.elmt, .qet structure)
* Code architecture improvements (ActionPool, serialization)
* Feature enhancements (intelligent numbering, xref)
* Code quality improvements
- Current release status (v0.100, Jan 2024)
- Qt6 migration status and active development
- 30+ open issues with priority levels
- How to contribute to roadmap
- No fixed timeline (honest about community-driven nature)
- Communication channels and learning resources
Research gathered from:
- GitHub repository structure and CONTRIBUTING.md references
- Release notes and build system (CMake)
- Dependencies (Catch2 v2.13.10, googletest v1.17.0)
- QET 2.0 refactoring document and technical vision
- Current open issues (30 total, with descriptions)
- Roadmap and architectural plans
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