Hi David, Am Samstag, 9. November 2013, 00:39:27 schrieb David Faure: > Hi Friedrich, > > I'm looking at interfaces/khexedit in kdelibs-frameworks, and wondering what > to do with it. > > Are you still happy with it? Should we bring it into the KF5 world? > > If so, we need to find a place for it. > > It's only header files so it could be installed by any framework without any > additional "cost" for the framework. > > The only dependency seems to be on kservicetypetrader.h, so we could move > the whole set of headers to the KService framework. > > Seems that the only implementor of the service is okteta, and the only user > of the service is kdevelop. But apart from a direct dependency of kdevelop > on okteta, or fragile dynamic stuff (invokeMethod etc.), I admit that I > don't see a better solution. > > Input welcome.
Once upon a time those interfaces were invented to enable KPilot (yes, those times) to be able to use the hexedit widget I did then, without having these rather specific widget in kdelibs or having kdepim depend on kdeutils (where the lib was then living hidden away in a khexedit subdir, while not used by khexedit itself). These days I know of no other user besides KDevelop as well (somewhere in the debugging area IIRC). But it has been proposed to use the Okteta libs directly there, as the Okteta libs are already used directly in another place in KDevelop (for the hex editing plugin). It just needs someone to do the coding. So from my point of view, especially given the idea of KF5, I see no more need for interfaces/khexedit. Rather do I see the Okteta libs themselves (the core ones for simple widget things) one day being added to KF5, now that things are modular :) Cheers Friedrich _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
