Re: Handle graphics again

[John W. Eaton]

On 13-Feb-2006, John Swensen wrote:

| Unfortunately, I have to side with Shai on this one.  I see the document
| portion of the handle graphics as the fairly trivial portion.

Perhaps it is trivial.  But there is still no reason to implement it N
times.

| It was also much much easier to implement
| the get/set for each "type" of object and enforce restrictions on values
| and such using simple inheritence and other OO tactics.

Yes, this could be an advantage of a C++ implementation.  OTOH, do you
really want this information embedded in compiled C++ code?  Shouldn't
it be stored in a data file, since the properties and constraints on
them are really just data?  It seems to me that we could store the
information in a file that is read when Octave first initializes the
handle graphics system.  Checking constraints on properties would then
be a matter of calling the appropriate constraint-checking function
for the given property.

Thanks,

jwe