Hi all, imho, these are changes that get mostly unnoticed, and hence close to no one will use this feature. I personally would find it very cool if there were lots and lots of blogs on the planet for these technical details. It would also communicate a bit more of the internals to potentially new developers. So feel free to interpret this mail as a call for more blogging ;)
Greetings Dominik On Tuesday 07 October 2014 20:04:26 Christoph Cullmann wrote: > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/120099/ > ----------------------------------------------------------- > > (Updated Oct. 7, 2014, 8:04 p.m.) > > > Status > ------ > > This change has been marked as submitted. > > > Review request for KDE Frameworks and David Faure. > > > Repository: kxmlgui > > > Description > ------- > > Instead of installing them in the kxmlgui5 share prefix, install them in a > kxmlgui5 prefix in resources. That will allow to test stuff without > installing it first, as the resources will be found anyway. Still the "I > can edit it and have a copy in my writable datadir" should work. Question > is: is it possible with one "kxmlgui" prefix for the resource or is it > better to swap that around like "componentname/kxmlgui5/.."? > > > Diffs > ----- > > src/kxmlguiclient.cpp e8170ad > src/kxmlguifactory.cpp c4ad97b > > Diff: https://git.reviewboard.kde.org/r/120099/diff/ > > > Testing > ------- > > Compiles & if I package ui file in kate into resource, works. > > > Thanks, > > Christoph Cullmann _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
