Well, currently the database is handled completely in JS using QML’s LocalStorage
API. Switching the database to C++ would mean rewriting everything from scratch.
Also, the entries are not so much stored as events bound to specific dates. I don’t know how a calendar-centric database could handle the two special cases “this week” and “sometime in the future” - how could that be synchronised? The app uses “magic” dates for these cases at the moment (→ code).
To be honest: I don’t :S. On the other hand, I want to put in some big changes anyway, so it will end with a complete rewrite in any case. But to me it seems completely overkill and way too much work for very little benefit.
That is, unless mKCal can give me a hand with “recurring” entries, i.e. entries that should be repeated every Xth of the month, every X days/weeks, every Xth weekday, etc. That’s something that would be tedious to implement with the current database.
Anyway, thank you very much for offering to help! I’d recommend that you take a look at the code (→ db, → rest) and decide yourself whether its doable without too much effort. You already know mKCal so it’s easier for you to gauge, I guess.