I have published a native Windows distribution of OmaWrite at
https://github.com/AbrarZShahriar/omawrite-windows, with compiled packages at
https://github.com/AbrarZShahriar/omawrite-windows/releases/latest.
The port keeps the Linux path intact and places the operating-system differences
at the existing platform boundaries:
- Windows theme detection uses Qt's native color-scheme API; the DBus and XDG
behavior remains on Linux.
- GitHub Actions builds and tests with Qt 6.8.3 and MSVC 2022 x64.
- windeployqt produces a dependency-complete portable ZIP.
- An Inno Setup package provides per-user installation, clean uninstall, and
registration as a Markdown application.
The current Windows test run passes 11 tests and skips the one Linux-specific
theme-file check. Release artifacts have companion SHA-256 files.
If Windows support fits OmaWrite's upstream scope, I can separate the core
portability changes from the downstream release and installer work into focused
pull requests. If it does not, the fork can remain a documented downstream
distribution.
I have published a native Windows distribution of OmaWrite at
https://github.com/AbrarZShahriar/omawrite-windows, with compiled packages at
https://github.com/AbrarZShahriar/omawrite-windows/releases/latest.
The port keeps the Linux path intact and places the operating-system differences
at the existing platform boundaries:
behavior remains on Linux.
registration as a Markdown application.
The current Windows test run passes 11 tests and skips the one Linux-specific
theme-file check. Release artifacts have companion SHA-256 files.
If Windows support fits OmaWrite's upstream scope, I can separate the core
portability changes from the downstream release and installer work into focused
pull requests. If it does not, the fork can remain a documented downstream
distribution.