notes

Yes, my FOSS note-taking app[1] used to be pure Qt Widgets. Recently, I've added the Kanban feature that uses QML (this and the editor settings should be the only parts in QML, if I remember correctly). [1] https://github.com/nuttyartist/notes

You can check my FOSS note-taking app: https://www.notes-foss.com. It is a native Qt C++ app. It has a feature that converts your Markdown tasks into a Kanban: https://www.notes-foss.com/videos/kanban.mp4 It doesn't have a built-in sync, but people have told me they managed to sync the DB using Dropbox and other such services. It has a one time payment option to unlock the Kanban feature, but you can also compile it yourself and get all the Pro features for free (all instructions are on GitHub[1]). [1] https://github.com/nuttyartist/notes

Hi there! Yes, I will switch to a more distinctive icon in the future once I can afford to hire a new designer. Multiplayer was quoting the correct reason. I also exeplained more about the timeline here: https://github.com/nuttyartist/notes/issues/690#issuecomment... Tldr: The FOSS version earned a stable revenue through Google Ads placed on the website, since the website ranked high on Google searches. Two years ago, that changed since the website got de-ranked, so I created a different, proprietary version of the app based on the FOSS version but with a totally revamped block editor that I wrote from scratch - that I worked on full-time for a whole 1 year.

I was wondering about that too. This is in the article linked to https://rubymamistvalove.com/block-editor 7. The previous version of Daino Notes, called Notes is FOSS (free and open-source software) available at https://www.notes-foss.com/ and the source code is available at https://github.com/nuttyartist/notes. I decided to make Daino Notes closed source due to difficulties in monetizing FOSS. In order to comply with Notes' MPL license, all common files between Notes and Daino Notes are published in https://github.com/nuttyartist/daino-notes-public

> I use Qt myself and one of the best things about the framework and toolkit is the UI tooling that allows me to drag and drop and visually create my UIs in the UI Designer app. But then it's not trivial to write responsive/adaptive applications. In contrast, QML makes it extremely easy to build such apps. I used to build UIs in the designer as well[1] but after studying QML there's no going back. Here's a new project I program solely in QML (and C++ for the logic)[2]. [1] https://github.com/nuttyartist/notes [2] https://www.get-vox.com/

I wanted to like Joplin but it's not very fast. It takes like 5 seconds just to start. So now I use: https://github.com/nuttyartist/notes

Thanks! I'm not 100% sure about this, still hearing feedback from people on both ends. Some reasons for the switch would be: 1. File versioning 2. Easier self-hosted syncing 3. Better data portability (although we already support exporting to .txt) I would love to hear counterpoints. Currently, SQLite works pretty well, and our custom database is pretty simple (plus, our database code is also open source[1]). [1] https://github.com/nuttyartist/notes/blob/master/src/dbmanag....

Hey, Waqar! If I’m not mistaken, you also contributed to my own Notes app https://github.com/nuttyartist/notes, so thanks! Can you please point where in Kate’s source code I’ll see the implementation for this? That would be super helpful.

This is true, but then again, these days, it's easy to look up at a popular open source Qt app and copy its CI recipes. For example, anyone that wants recipes for creating binaries for multiple operating systems can copy the GitHub workflows in my open source note-taking app: https://github.com/nuttyartist/notes/tree/master/.github/wor... That said, I really think Qt should have a separate commercial license that is exactly like LGPL but allows you to link statically and costs much less (without all the enterprisy things).

Plume is actually based on my open source note-taking app Notes[1]. You can already get it on Flathub, Snap Store etc. Notes uses just a simple plain text editor while Plume has a completely revamped block editor that I built from scratch. That parts of Notes used in Plume will remain open source (per the MPL license) but the rest of the code will be closed source. At least for the time being. [1] https://github.com/nuttyartist/notes

Haha, they're both my creation (: Plume is based on Notes (https://github.com/nuttyartist/notes). I believe I'll change the icon before Plume's release.

> most devs are not comfortable with linking/packaging/dependency management Using `macdeployqt`, `windowsdeployqt` and `linuxdeployqt` takes care of that in mostly one click. I used to look at other open source apps workflows to figure it out. Now, others can look at my app's workflows for a complete packaging experience for Windows, Linux, and macOS[1]. Huge credit to contributors for my OSS app for implementing and perfecting it. [1] https://github.com/nuttyartist/notes/tree/master/.github/wor...

Safety-wise, the chance of choosing a non-safe new car today is very low since they're not on the market (a lot due to current regulation). > A privacy policy is a pinkie promise. Why depend on something so fragile for such an important function in your life, when there are much more trustworthy options? Logseq, Org Roam, and Joplin immediately come to mind. Yep, I agree. This is why my own previous note-taking app is completely open source[1]. But this comes with many difficulties, and often times subpar experience compared to closed source apps. That's why I decided to close source my next note taking app[2]. [1] https://github.com/nuttyartist/notes [2] https://news.ycombinator.com/item?id=38584960

Plume is built on top of my open source note-taking app Notes[1]. Since Plume is based on Notes, I'll of course comply with the MPL license and release all existing files that were changed (and must stay MPL licensed). But I recently discussed my reasoning to go close-source[2]. I've been working night and day (every day) converting 4 cups of coffee into code for the last 4.5 months to create Plume. I don't want to risk not being rewarded sufficiently for it. But, I'm 99% sure that I'll either open source the core block editor or the entire app in the future. [1] https://github.com/nuttyartist/notes [2] https://news.ycombinator.com/item?id=38584960

These are all great questions. 1. Notes is completely open-source[1]. There are some awesome maintainers who help me fix and update things and sometimes even implement new features. When Plume will be released, of course, I'll put much less time into Notes (as already the case). But since Notes is licensed under MPL and Plume is built on top of it, all files used from Notes will be open source as well, so any improvement from Plume could be potentially incorporated into Notes. 2. The reason for creating Plume is that I always wanted[2] to create an advanced editor (a la Notion) but only recently realized how to be able to do it using C++ (handling the model) and QML (handling the view). I had to implement many things from scratch (undo/redo/copy/paste/multi-block-editing/etc). 3. I recently discussed my reasoning to go close-source[3]. I'