A meta-project which contains all tasks and repositories related to packaging and releasing KDE software in desktop versions of Windows.
Thu, Jan 16
Sounds releaseable. Crashes just make a good impression, do you want to release it. We might add a beta disclaimer to the description?
The current package of the 19.12.1 release built with KDE Frameworks 5.66.0 has still one bug:
Dec 17 2019
Opening the settings dialog the first time takes quite long, clicking it the second time crashes elisa.
Maybe you should investigate before we release ^^
Dec 16 2019
MS is not necessarily well liked by KDE users
A simple music player that should be easy to use. It does not require any configuration before one can use it. It will read all your music.
The screenshot of Elisa running on Windows is here https://community.kde.org/File:Elisa-windows.png
Dec 12 2019
Dec 10 2019
Dec 8 2019
Dec 7 2019
Yes it works :)
Dec 4 2019
I would agree that a UNIX/POSIX env var is not the most logical thing to use on Windows, but how do we ensure that we are in sync with ki18n? The usage of QLocale in ki18n looks like it is just adding extra languages to a list of languages, not actually using QLocale to determine what catalog to load. At least LANGUAGE overrides any QLocale settings. Should ki18n not be moved to using QLocale and setDefault()?
So the conclusion is that we are not using setDefault() yet and ki18n & gettext uses the LANGUAGE env so the logical thing, for now, is to also use LANGUAGE env here in KCoreAddons for the plugin metadata translations?
Dec 3 2019
Dec 2 2019
Dec 1 2019
Well it sounds to me like we might need both.
But the issue this pr tries to tackle would probably be gone with setDefault
ki18n does not seem to use QLocale to get the language for translation, but uses LANGUAGE env. Also gettext uses the env variable.
To be honest i don't remember why we don't use setDefault.
Why can't we use setDefault?
Your linked patch does not look like it would change the behaviour on Windows?
Right, but we set it in initializeLanguages.
The doc doesn't mention the LANGUAGE var.
Nov 28 2019
Nov 25 2019
Nov 17 2019
Nov 13 2019
I've also got access to the partner center now. So, I can handle updates from now on. Thanks again!
Nov 12 2019
It is online ;=)
Nov 10 2019
Perhaps you could apply for some account to the partner center to be able to do updates yourself.
It will appear at this location in the next days:
Ok, will grab your screenshots and give that a try for submission, thanks!
Build 566 works fine now.
Nov 9 2019
I've added a patch to disable Sonnet's language auto-detection during the first run of Kile.
Nov 6 2019
sure they can.
get the dev version of falkon and go to https://store.falkon.org/p/1301207/
This one is in Qml
And QML plugins can be packaged and hot swapped on a compiled browser?
Please correct me if I'm wrong
There is Qml, maybe Qml API needs a but more work but in general it works.
To close off the rant about the workflow on KDE: it's not that there's many tools, it's that there's so many different tools that all use different logins. For the bug tracker I don't need a KDE identity account, for Phabricator I do. Why keep the bug tracker seperate from the projects? Makes no sense, as you're missing overview this way.