Re: the kspeech interface

2013-11-10 Thread Kevin Ottens
On Saturday 09 November 2013 11:47:16 David Faure wrote: > On Friday 08 November 2013 22:45:33 Jeremy Whiting wrote: > > Could we move the dbus interface into > > kdeaccessibility/jovie and install it only when jovie is installed, > > This would create a compile-time dependency on kdeaccessibility

Re: the kspeech interface

2013-11-09 Thread David Faure
On Friday 08 November 2013 22:45:33 Jeremy Whiting wrote: > 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 a

Re: the kspeech interface

2013-11-08 Thread Jeremy Whiting
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,

Re: the kspeech interface

2013-11-08 Thread Jeremy Whiting
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 does

the kspeech interface

2013-11-08 Thread David Faure
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