[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC] octave-to-backend notification of property change
From: |
Michael Goffioul |
Subject: |
Re: [RFC] octave-to-backend notification of property change |
Date: |
Mon, 7 Jul 2008 11:54:31 +0200 |
On Sun, Jul 6, 2008 at 11:57 AM, Maciek Gajewski
<address@hidden> wrote:
> But I can't understand why backend developers (*ehem* me *ehem*) have to be
> forced to use this scheme.
That's a weird statement: "octave's design does not fit well with my code
and I don't see why I should be forced to use octave's design"...
> Just three methods would do the magic:
> - property_changed( handle, name )
> - object_added( handle )
> - object_removed( handle )
Come with an appropriate changeset and we'll discuss it further.
Michael.
- [RFC] octave-to-backend notification of property change, Michael Goffioul, 2008/07/04
- Re: [RFC] octave-to-backend notification of property change, David Bateman, 2008/07/04
- Re: [RFC] octave-to-backend notification of property change, Maciek Gajewski, 2008/07/04
- Re: [RFC] octave-to-backend notification of property change, Michael Goffioul, 2008/07/04
- Re: [RFC] octave-to-backend notification of property change, Maciek Gajewski, 2008/07/04
- Re: [RFC] octave-to-backend notification of property change, Michael Goffioul, 2008/07/05
- Re: [RFC] octave-to-backend notification of property change, Maciek Gajewski, 2008/07/05
- Re: [RFC] octave-to-backend notification of property change, Michael Goffioul, 2008/07/05
- Re: [RFC] octave-to-backend notification of property change, Maciek Gajewski, 2008/07/06
- Re: [RFC] octave-to-backend notification of property change,
Michael Goffioul <=