Re: handle graphics

[Ole Jacob Hagen]

Hi

I believe that Octave should not be aware of "handle 
graphics"-properties, since handle graphics should be handled by each 
visualisation application/plugin.
Octave should provide a "handle-graphics"-layer, that should be used by 
each visualisation application.

As you know, Oplot and Props is implemented in this way.
Octave (as m-script) checks if data is of correct type, and sends the 
data to Oplot. Communication layer of Oplot receives these data, and set 
the respective Props-data.
Since visualisation classes in Oplot inherites the property-callbacks 
from Props, the callbacks are executed. Each visualisation classes 
handles each of this callbacks separately.

Another point.
If Octave is aware of handle graphics object, wouldn't this result in 
multiple duplications of same data, both in Octave, and visualisation 
application?
This should be avoided. Or do people want handle graphics to be 
implemented as references to datasets?
An example:
v = randn(1,100);
h = plot(v)
would then result in one instance of v, and h-g implementation in Octave 
gives a reference/pointer to v?
In visualisation application the same data would exist both in 
application and graphics card?

If I implement the behaviour found in CMO into Props, Oplot could send 
back to Octave, and not only as replies, since a event-loop on Octave 
side is required.

Cheers,

Ole J.