On Wednesday 29 August 2012 23:53:32 David Faure wrote: > KPluginLoader itself depends on KLocale, since it automatically > inserts the translation catalog for the plugin. I think that's a good > feature, it's part of what makes klocale superior to qtranslator, so the > only solution would be that kservice is tier2, and depends on the klocale > framework.
And of course KPluginLoader also depends on KComponentData, to describe plugins. I'll move that too, to the kservice framework... And KComponentData has "KStandardDirs* dirs()"... oh man. Seems rarely used though, I'll try removing that. KAboutData is already in kcoreaddons, but with broken localization. I think I'll move KAboutData up to kservice, to repair that. The idea being, old code keeps working this way, and new code doesn't need KAboutData in main(). .... well, except for the about dialog. This means all apps end up needing the hopefully-deprecated-at-some-point kservice. This makes me wonder if KAboutData should go into the klocale framework then -- it's a simple data container, but which depends on klocale. In any case this means I need to make a klocale framework first. Seems hard to fix compilation today then. I'll try reverting in "frameworks" and moving this work to a branch. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
