Re: handle graphics

[Shai Ayal]

I kind of liked the idea of no distinction between objects and
properties, but never mind.

As you can see from the other responses to your email, at least 3
projects are actively pursuing this goal. All 3 have implemented this
tree structure, each in a different way. If indeed emulating matlab
handle graphics will become an "official" goal of octave, this could
be manifested by have an "official" object/property tree in octave as
you propose.

Shai

On 7/12/05, John W. Eaton <address@hidden> wrote:
> On 12-Jul-2005, Shai Ayal wrote:
> 
> | In your proposal there is no clear distinction between object and
> | properties, in a sense everything is a property of the "root".
> 
> Maybe my description wasn't clear.  The structure I presented was a
> form of a tree, and at each level of the tree, you would have some
> properties and some other graphics objects.  I think we could further
> simplify this so that each graphic object is a structure with four
> elements:
> 
>   id            a serial number, so we can look up this object given a handle
>   parent-id     so we can go up the structure if necessary
>   properties    a structure array of (name, value) pairs
>   children      an array of other graphics objects
> 
> jwe
>