On 10/4/07, Chady Kassouf <[EMAIL PROTECTED]> wrote:
>
> On 10/4/07, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote:
> > On 10/4/07, Chady Kassouf <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > On 10/4/07, Gustavo Sverzut Barbieri <[EMAIL PROTECTED] > wrote:
> > > > [...snip...]
> > > > As I sa
On 10/4/07, Chady Kassouf <[EMAIL PROTECTED]> wrote:
> > My idea is to vanish with signal, type and properties from users
> > headers, they should remain internal to etk machinery.
>
> What is the proposed replacement then?
I think he meant have a connect() (and a disconnect, block, unblock)
as me
On 10/4/07, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote:
>
> On 10/4/07, Chady Kassouf <[EMAIL PROTECTED]> wrote:
> >
> >
> > On 10/4/07, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote:
> > > [...snip...]
> > > As I said before, it would be great to have
> > > connect() as a method of
On 10/4/07, Chady Kassouf <[EMAIL PROTECTED]> wrote:
>
>
> On 10/4/07, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote:
> > [...snip...]
> > As I said before, it would be great to have
> > connect() as a method of object, not signal.
> >
> >
>
> That's actually what I have done in etk-perl
> t
On 10/4/07, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote:
>
> [...snip...]
> As I said before, it would be great to have
> connect() as a method of object, not signal.
>
>
That's actually what I have done in etk-perl
the SignalConnect is a method of Etk::Object from a user's point of view,
On 10/3/07, Enlightenment CVS <[EMAIL PROTECTED]> wrote:
> Enlightenment CVS committal
>
> Author : cmarcelo
> Project : e17
> Module : libs/etk
>
> Dir : e17/libs/etk/src/lib
>
>
> Modified Files:
> etk_signal.c etk_signal.h
>
>
> Log Message:
> Minor changes in signals.
>
> - export
