It's just very small Qt app which usually lives in your system tray and allows you to make notes quick way.
QtNote was written as a clone of Tomboy with use of Qt. It's not so feature rich as Tomboy but light and fast and usually suits all common needs. Moreover QtNote can work with Tomboy notes and it's not so hard add support of other apps.
Some features:
- Quick access to notes from tray menu
- Internal notes manager to handle multiple notes at once / search notes
- Support for Tomboy/Gnote notes
- Support for markdown
- Create notes from selection by a hotkey
- Spell checking (hunspell)
- Cross-platform (tested on Linux and Windows with gcc and Visual Studio)
- Other: configurable amount of notes in menu. configurable storage path, print note, save note dialog geometry
Check https://github.com/Ri0n/QtNote/releases page for the latest downloads.
Some older releases could be found at https://yadi.sk/d/HbnqnaTN6fwzN.
QtNote requires:
- a C++20 compiler;
- CMake 3.25 or newer;
- Qt 6.4 or newer with the Core, Gui, Widgets, PrintSupport, Network, and XML modules;
- QCA 2 built for Qt 6;
- QtKeychain built for Qt 6.
The default Linux configuration also uses Qt DBus and Qml. Qt Test is required
when configuring with BUILD_TESTING=ON, which is the default.
Optional dependencies enable additional features and plugins:
- Qt Multimedia for audio recording;
- Xlib development files for
baseintegrationand other direct X11 support whenQTNOTE_ENABLE_X11=ON(the default on Linux); - Hunspell for spell checking;
- ECM, KDE Frameworks 6 (Config, CoreAddons, GlobalAccel, Notifications, and WindowSystem), and Plasma 6 development files for KDE integration;
- QXmpp 1.11 or newer with OMEMO, QCoro, and Qt Network/XML for XMPP PubSub
storage. Alternatively, configure with
QTNOTE_BUILD_BUNDLED_QXMPP=ON; the bundled build additionally requires OpenSSL 3 andlibomemo-c.
On Plasma 5 systems, use an X11 session with baseintegration. The native KDE
integration targets Qt 6, KDE Frameworks 6, and Plasma 6; Qt 5/KF5 builds are
not supported.
Configure and build QtNote with:
cmake -S . -B build
cmake --build build -j
cmake --install buildThe install step is optional. Its default prefix is normally /usr/local; set
another one during configuration with, for example,
-DCMAKE_INSTALL_PREFIX=/usr.
To list QtNote-specific configuration options after configuring the build directory, run:
cmake -LA -N build | grep QTNOTEThe principal options are:
QTNOTE_DEVEL— use development resource and plugin search paths;QTNOTE_ENABLE_X11— build components which access X11 directly;QTNOTE_BUILD_BUNDLED_QXMPP— build the bundled QXmpp fallback;QTNOTE_PLUGIN_ENABLE_<name>— enable or disable an individual plugin. Plugins default to enabled when the platform and their dependencies support them.
Check ./admin/{deb,rpm}build.sh scripts. You can start them w/o arguments.
You need conan in your PATH. It's up to you how you install it. Then you need to enable Conan support in Qt Creator plugins. You need cmake and ninja in PATH too because Qt Creator doesn't pass their locations to Conan (just add those installed by Qt Maintenance tool). The remaining magic should work automatically.
To build an installer wix.exe from WiX toolset also has to be in PATH.
Follow next steps after installing dependencies and configuring PATH:
- select release build in qt creator
- build it (ctrl + b)
- then update deployment configuration and 2 steps in exact order
- cmake install
- cmake build of
burn_installertarget
- try to run and this will execute the deployment.
- deployment creates QtNote installer, so check terminal for logs.
https://app.transifex.com/rion/qtnote
- note encryption (not yet decided if own implementation or some integration)
- note tags + AI-based classification
- more plugins for various popular systems