octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: handle graphics


From: Shai Ayal
Subject: Re: handle graphics
Date: Wed, 13 Jul 2005 06:48:24 -0500

To me is seems that CMO, being the most abstract, will probably be a
good start. However I know almost nothing about it, so Driss will have
to fill us in on this.

>From the little he did write, it is almost struct like in the sense
that object.property syntax is already implemented and it does have
facilities to communicate with external modules.

Shai

On 7/13/05, John W. Eaton <address@hidden> wrote:
> On 12-Jul-2005, Shai Ayal wrote:
> 
> | I kind of liked the idea of no distinction between objects and
> | properties, but never mind.
> 
> If we put all the properties for a given object together in a
> structure array, then listing all the possible property names for a
> given object is trivial:
> 
>   fieldnames (object.properties)
> 
> so I think there is some advantage.
> 
> | 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.
> 
> Yes, think it would be bad to have N separate implementations of this.
> 
> jwe
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]