+1 to add-on. Later, we could probably make an accessibility backend on top of it, too.
Regards, Konstantin 2014/1/17 Frederik Gladhorn <[email protected]> > Fredag 17. januar 2014 18.17.57 skrev Kevin Krammer: > > On Friday, 2014-01-17, 17:43:40, Frederik Gladhorn wrote: > > > Fredag 17. januar 2014 16.13.16 skrev Kevin Krammer: > > > > On Friday, 2014-01-17, 14:42:37, Travis Allen wrote: > > > > > On Fri, 2014-01-17 at 14:21 +0100, Frederik Gladhorn wrote: > > > > > > So this is a request for a repository, playground/qspeech (?). > And > > > > > > I'm > > > > > > also open for a name for the repo and "module". > > > > > > > > > > We will want to be able to do the reverse Speech To Text as well > > > > > (if/when/where available). QSpeech as a repository sounds > reasonable > > > > > to > > > > > me. > > > > > I can't come up with a better one. > > > > > > > > > > Should they be the same module or different modules? Initially I am > > > > > leaning > > > > > towards different modules because some platforms may have one way > but > > > > > not > > > > > the other. However on other platforms they may be tightly coupled > so > > > > > there > > > > > could be some code re-use between the two modules. > > > > > > > > I could imagine that the respective system dependencies could rather > > > > different, i.e. speech input and speech output having asymetric > > > > technology > > > > requirements. > > > > > > > > In which case a single module would drag in both. Are both likely to > be > > > > used together or could there be common cases which use only one of > them? > > > > > > That really depends on the application, but no matter what we can even > > > have > > > two libraries in one module/repo, so I wouldn't mind having both in one > > > place unless one of them grows huge. > > > > I was mostly thinking about consequences of > > QT += speech > > > > This would make the application link against both libraries, no? > > Sure, but it hasn't been released yet ;) > I'd get it started and then see where we end up. I do think this is great > input and I will have to rename my stuff to not use qspeech but something > that > implies tts in the classes so that the recognition part can coexist nicely. > > Thanks for the feedback. > > Frederik > > > > > Cheers, > > Kevin > > -- > Best regards, > Frederik Gladhorn > Senior Software Engineer - Digia, Qt > Visit us on: http://qt.digia.com > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development >
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
