[Sugar-devel] [GSoC 2014] Sugar Listens Weekly Summary

[Rodrigo Parra]

Hi Sam!

First of all, thanks for your time and suggestions.
Here's my second blogpost http://tmblr.co/ZLEL4t1HZ7XRT and as you said, it
seems like having a central recognizer process is the way to go.

As for the language model, believe me, it is not as scary as it sounds!
We plan on providing default models if available, but letting each
developer override the language model with a grammar is a huge gain in
terms of flexibility and accuracy.

A simple language model is very easy to define, and with good docs (which
are on the roadmap) I think developers will be fine.
Regards,

Rodrigo


2014-05-28 7:05 GMT-04:00 Sam Parkinson <sam.parkinson3 at gmail.com>:

> Hi Rodrigo!
>
>
> It is nice to see 'Sugar Listens' getting developed! It sounds really cool.
>
>
> As for the architecture you are suggesting I think design 1 (the central
> process) would be the best way go.
> Memory usage is a REALLY important thing on the xo, and a dbus based
> design will make building a js (or whatever other language) api easier.
>
>
> From what I can gauge, it appears you are trying to have always on voice
> recognition (please tell me if I'm wrong), which is pretty cool!
> Having multiple sphinx instances all listing at the same time would not be
> very good.
> Having a centralized one would let you only send events only to the
> current activity, and maybe default back to the system.
>
>
> Your Blog> IPC message load: delay introduced by IPC calls should be
> considered.
> Doing some benchmarks would be cool, this sounds like a tiny issue to me!
>
>
> Your Blog> Each Activity can provide its own language model...
> That sounds scary!
> I think, as powerful as that would be, it is really important that you
> resist the temptation to shove really complex stuff onto activity
> developers and force them to learn about it (sorry for being a hypocritical
> there).
> Make sure you have a good default (if that is possible, I don't know
> anything about language models)
>
>
> As for the api functions names, IMHO we should use some GTK terminology
> (like connect instead of listen).
>
>
> Looks like a great start to an exciting project!
> Sam.
>
>
> On Wed, May 28, 2014 at 9:06 AM, Rodrigo Parra <rodpar07 at gmail.com> wrote:
>
>> Hello everyone,
>>
>> To sum up last week's activities for my GSoC project I wrote an article
>> in my personal blog. My project is called TamTam Listens and my mentor is
>> tch.
>>
>> If you want to take a look, here's the link:
>> http://tmblr.co/ZLEL4t1Gv4jqp
>>
>> As stated in the article, constructive feedback about the architecture,
>> the API or the article itself is more than welcome.
>>
>> Best regards,
>>
>> Rodrigo Parra
>>
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140602/5e17efa9/attachment-0001.html>