Re: [tuxdroid-user] C++ Library

[Neil A. <arm...@po...>]

Hello,

I ported most of the basic functionalities in c# with mono using the =20
tcp socket connexion with tuxdaemon,
you can grab the code at : http://stream.dedale.eu.org/tuxdroid
I was part of a school project, and we made an UPnP connectivity for =20
tuxdroid, except for the voice part (which was a bit complicated in c#).

Neil

Le 3 f=E9vr. 08 =E0 08:51, David Bourgeois a =E9crit :

> On Sat, 02 Feb 2008 05:33:55 +0100, Henry de Valence
> <hde...@gm...> wrote:
>
>> On Friday 01 February 2008 7:22:20 pm Alan Trick wrote:
>>> I'm not an expert on the code at all, but I think the real code is
>>> actually in C (with python bindings). It's not quite the same, but =20=

>>> it
>>> should work.
>>
>> Hmmm.. Is this in the SVN repo ? I presume it's GPL2+, right?
>
> The daemon is written in C, it's on SVN. For now it opens a port and =20=

> the
> python API connects to it and offer _a_lot_ of other functionalities.
> Parts of the daemon are currently rewritten as a Library. It's =20
> mostly the
> parts that deal with the USB and hndles commands and status from =20
> tux. That
> library will be used to rebuild the same daemon but you could also =20
> choose
> to bypass the daemon/python API and use the library directly.
>
> Now we thought about something better than the current daemon, like
> xml-rpc so you could use any language (xml-rpc clients exist in most =20=

> of
> them) to address your tux very easily.
>
> Cheers,
> David
>
> =
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> tux-droid-user mailing list
> tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tux-droid-user

--
Neil ARMSTRONG
Etudiant Polytech'Nice-Sophia D=E9partement Sciences Informatiques
www.dedale.eu.org
arm...@po... (PGP : 0x05834E84)
nei...@gm...
Jabber: su...@ja...