As I recall, the possibility of creating a push to talk service that could be used within any activity (provided by default as part of the activity class itself) was discussed not too long ago as well. I think this may be a smart option, especially since a push-to-talk activity would be visually pretty sparse anyway, and this way every Sugar activity can take advantage of it.
- Eben On Dec 12, 2007 10:55 PM, Walter Bender <[EMAIL PROTECTED]> wrote: > Just as a reminder, there is push-to-talk already built into EToys, > though I haven't tried it for awhile--it certainly used to work just > fine. > > -walter > > > On Dec 12, 2007 9:33 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: > > although full voip would be nice, simply adding voice to chat in a > > push-to-talk fashion might be nice, too. i don't see why we shouldn't > > do both, unless the exact same people are invoved. > > --scott > > > > > > On 12/12/07, Sjoerd Simons <[EMAIL PROTECTED]> wrote: > > > On Wed, Dec 12, 2007 at 11:21:59AM -0500, Benjamin M. Schwartz wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hash: SHA1 > > > > > > > > Benjamin M. Schwartz wrote: > > > > > 4. Longer description : Support voice conversation using voice > > > > > IM > > > > > : between any two XO in a local mesh or > > > > > : globally, using the XO presence > > > > > : infrastructure > > > > > > > > This would be welcome. VoIP has been part of the plan from the > > > > beginning, > > > and > > > > there's even a draft implementation at > > > http://wiki.laptop.org/go/Push_to_Talk > > > > and early discussion at > > > > http://dev.laptop.org/ticket/22 > > > > > > > > VoIP development is currently blocking on Telepathy-Salut, which is our > > > > serverless communication manager. Telepathy-Salut does not yet > > > > implement > > > any > > > > real-time channels (e.g. RTP), so there is no clean way to build VoIP > > > > into > > > the > > > > presence infrastructure when not connected to the global internet. > > > > > > That is quite an overstatement. It is true that salut at currently doesn't > > > support the telepathy interfaces needed for video conferencing. Which does > > > indeed mean we can't do VOIP when not connected to the internet at this > > > point. > > > Adding jingle support on salut is planned, but untill now we had other > > > priorities :) > > > > > > This does not mean VOIP development is blocked on salut though.. Gabble > > > does > > > support the needed bits for VOIP. So you can continue work on the Video > > > Chat > > > application right now, without needing to wait on salut. Also thanks to > > > the > > > beauty of the telepathy design, as soon as salut starts support VOIP, it > > > will > > > work with the VOIP activity without any changes. So this work can be done > > > in > > > parallel. > > > > > > And last but not least, Connection manager never implement RTP or other > > > real > > > time channels themselves, they just do the signalling. All the actual work > > > of > > > sending and receiving the media is done by another component called > > > stream-engine which is independant of the protocol used for signalling. > > > > > > > > > Sjoerd > > > -- > > > Life exists for no known purpose. > > > _______________________________________________ > > > Devel mailing list > > > [email protected] > > > http://lists.laptop.org/listinfo/devel > > > > > > > > > -- > > ( http://cscott.net/ ) > > > > _______________________________________________ > > Devel mailing list > > [email protected] > > http://lists.laptop.org/listinfo/devel > > > > > > -- > Walter Bender > One Laptop per Child > http://laptop.org > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.laptop.org/listinfo/devel > _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
