Michael Jennings wrote:
> On Sunday, 11 March 2007, at 15:53:28 (+0100),
> St?phane Bauland wrote:
>
>
>> Ok! In fact, ecore_proto is not an abstraction layer to im
>> protocol. It needs to support all type of protocol (ie. im, ftp,
>> http, sftp, etc...) So we dont need telepathy.
>>
>
>
On Sunday, 11 March 2007, at 20:36:57 (+0100),
Vincent Torri wrote:
> would it mean that you do not want me to add ecore_xcb ? :p
ecore_xcb makes sense. ecore_metric_fuckton_of_random_protocol_bullshit
does not.
Michael
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTEC
On Sun, 11 Mar 2007, Michael Jennings wrote:
>
> Okay, first off, NO MORE ecore_* crap! Enough already!
would it mean that you do not want me to add ecore_xcb ? :p
Vincent
-
Take Surveys. Earn Cash. Influence the Future
On Sunday, 11 March 2007, at 15:53:28 (+0100),
St?phane Bauland wrote:
> Ok! In fact, ecore_proto is not an abstraction layer to im
> protocol. It needs to support all type of protocol (ie. im, ftp,
> http, sftp, etc...) So we dont need telepathy.
Okay, first off, NO MORE ecore_* crap! Enough a
Gervais Mulongoy wrote:
> Hi Stephane,
>
> HEH, well you can see that I am still quite new at this.
>
> So how do you want to proceed? Telepathy is a framework and the
> components are: Connection Managers, Client Library, Galago, Mission
> Control, and Streaming Engine. This is from
> http://te
Hi Simon,
yes, these functions make sense only for etk-perl, and the reasson for these
is that I cannot use va_lists in perl xs, so I will have to manually count
the arguments and do proper casting, so with 5 possible columns per item,
and 2 possible types per column, it's a combinatorial explosio
