Oops, that link was just users of soPlainText. It seems http://lxr.kde.org/ident?i=KSpeech the class itself is used in quite a few places, and is how any application uses speech capabilities. I guess kdbusaddons is as good a place as any for it and it will need to stay in kdelibs itself.
On Fri, Nov 8, 2013 at 10:40 PM, Jeremy Whiting <jpwhit...@kde.org> wrote: > I was actually wondering that myself the other day as I added to it in > kdelibs master (that got branched into KDE/4.12) for a feature that > hit jovie in KDE SC 4.12. > > It's used but really only needed to expose jovie's dbus interface for > applications to use. Interestingly, knotify uses jovie but doesn't > include kspeech.h somehow. Could we move the dbus interface into > kdeaccessibility/jovie and install it only when jovie is installed, > and use the dbus interface the same way it is used in knotify in the > places it's currently used directly? > > Jeremy > > On Fri, Nov 8, 2013 at 5:53 PM, David Faure <fa...@kde.org> wrote: >> Hi Jeremy, >> >> I'm looking at kdelibs-frameworks/interface/kspeech, and trying to find a >> home >> for it, in the KF5 reorganization. >> >> I see that it's actually used in a number of places >> (http://lxr.kde.org/ident?i=soPlainText for instance). >> and that it's basically just a header file that depends only on QtCore, >> plus some data files (dbus xml, desktop file). >> >> Are you still happy with that interface? >> Any idea where it would belong, in KF5? >> Maybe in kdbusaddons, since it's only usable with a dbus dependency? >> >> -- >> David Faure, fa...@kde.org, http://www.davidfaure.fr >> Working on KDE, in particular KDE Frameworks 5 >> _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
