Thanks Myriam and Heiko! Here are few comments:
* About the DB, I suggest the following text: "Mysql embedded has been
discontinued, so will be MariaDB embedded in a near future. So the
upcoming 3.0 version will see a port to a new DB backend;"
* the new scripting engine does not use QML at the moment. But it
probably will in the future because many features from Qt4 are not
present in QJSEngine. For example, it does not export QT widgets. Thus
scripts that contained windows or menus can't be exhibited. Using QML
here would be the obvious alternative. But imposes big changes in the
existing scripts.
Once Myriam publishes the release at the main page, then I will notify
all the relevant places
Cheers,
Pedro
On 2021-02-04 12:08, Heiko Becker wrote:
On Wednesday, 3 February 2021 16:56:42 CET, Myriam Schweingruber wrote:
Please everyone, have a look at the article on the web page, the
draft can
be found here:
https://amarok.kde.org/en/node/889
Thanks! A few notes:
* Not entirely sure how to phrase that best to avoid confusion, but
there were *no* changes inside Amarok to discontinue support for MySQL
embebbed. If you still have a version with it, it should work. Or if
you want, with a full blown MySQL database server.
* "The upcoming 3.0 version will see a port to a new DB backend;"
To my knowledge, that's not (yet) true. Due to the aforementioned
removal of the embedded lib from MySQL (and possibly from Mariadb in
the future as a consequence) this would certainly be welcome. I heard
somebody talk about working towards SQLite, which would also easily
work in flatpaks, but probably comes with performance pains at least
with huge collections. Anyway I haven't heard anything of that since
quite some time.
* The new scripting engine does indeed use QML, but Pedro is the
better person to talk to about this.
* Qt5/Qt4 looks nicer than QT5/QT4, is the official style by the QtC
and would also be consisten with the usage in the first sentence.
Best regards,
Heiko