On 03/11/2015 10:26 PM, Kevin Kofler wrote:
Glenn Holmer wrote:
https://bugs.kde.org/show_bug.cgi?id=340982
As I wrote in https://bugs.kde.org/show_bug.cgi?id=340982#c6 :
This is a regression resulting from the switch from KDE's powerful locale
and formatting classes to the inferior Qt-only ones, as part of the
Frameworks initiative (that aimed at reducing interdependencies between KDE
classes so that KDE can now ship a bazillion small "Frameworks" instead of a
single coherent kdelibs framework). Sadly, loss of functionality was not
considered a blocker for any of those K*→Q* ports.
This is a biased and incomplete explanation. While I
personally lament the loss of KLocale's functionality
as well, the motivation in switching to Qt's locale
system was mainly that the behavior and scope it im-
plements aligns closely with the rest of desktop
Linux, which KLocale always had trouble mapping to -
application of settings and behavior is now more con-
sistent between KDE's apps and other Qt apps, as well
as Linux desktop apps not using Qt at all.
Further, KDE contributed extensively to QLocale in
Qt 5 to expand and improve it, to make the port
feasible at all.
Finally, loss of functionality was generally con-
sidered something to avoid in moving to the Qt/KF5
architecture, and KDE contributed tens of thousands
of lines of kdelibs code and new code to Qt to help
avoid it. In specific cases - like this one -
functionality was lost, but not without thought or
reason.
Kevin Kofler
Cheers,
Eike
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
