Hello,
Here are my dreams for an interface kmatplot/octave. I can eventually giv=
e a=20
hand to concretize that.=20
Please, don't hesitate to critic and comment the following list:
1=B0) Like I said in a preceeding mail, a function=20
kcolormap(<colormap_string>)
to control the colormap of any plots will be great with a set of predefin=
ed=20
colormap (matrices Mx3 for M>=3D1)
2=B0) A couple of function kset/kget to control the object tree of kmatpl=
ot=20
through octave exactly like get and set do that in matlab.=20
In other words,
the command
kget(<object_number>)
kget(<object_number>,<property_name>)
would give respectively a complete list of the properties of the object=20
refered by <object_number>, or the value of the <property_name> belonging=
to=20
this object.
And the command
kset(<object_number>,<property_name>,<property_value>)
would set <property_name> to <property_value>.
3=B0) a function=20
kview(azimut, elevation)
to control the camera position around a 3D plot
4=B0) a function=20
kginput(n)
to obtain n coordinates on a 1D and 2D plot by clicking n times on it
5=B0) functions like
kxlabel(<string>)
kylabel(<string>)
kzlabel(<string>)
ktitle(<string>)
to write the xlabel, ylabel, zlabel (if 3D) and title through octave.
6=B0) and finally, a function
kprint <options> <filename>
kprint <other_options> <printername>
to export the current figure in $PWD in various format like EPS, QT Metaf=
ile,=20
Bitmap, JPEG, or to send figure to a given printer.
These six points represent the only wall for me to adopt completely Octav=
e=20
instead of Matlab. I think I'm not the only one in that case.=20
Kmatplot is a great step for that.
Bye,
Laurent.
|
