Re: [Kmatplot-general] Documentation

[Hugo v. d. M. <s13...@ba...>]

> > In my experience, kmatlot dies if one passes it e.g. kmesh(g), but is
> > happy if you pass it kmesh(x,y,g). I have to replace meshgrid(1:256)
> > with meshgrid(1:40) though, as anything larger causes the graph to not
> > be displayed. With it displayed, it's a set of vertical planes, not a
> > nice meshed surface...
> 
> Strange limitation. It's a bit annoying.

Is there a BTS somewhere for kmatplot, where one can also report
wishlist items, etc?

> Kamil, it's a detail but, is the kaddaxes procedure is absolutely necessary 
> in Octave ? 
> I think that a good use for a kmatplot "octaved" will be to approach the 
> matlab way where you have no equivalent of kaddaxes.

I think that while it is useful to be able to access different sets of
axes from octave, ideally it should also be more "directly compatible"
with what people already know. I would suggest that if a call is made to
kmesh or kplot etc. before a call to kaddaxes has been made, that axes
could be created automatically?

At a later version, if one wants more compatibility, one would want to
have a "hold" clone as well. It is always difficult to remain
"compatible" with existing solutions, while at the same time trying to
develop something new with more features. Hence maybe there needs to
(eventually) be "two modes" of operation, one compatible as far as
possible, the other - possibly turned on as soon as any of its features
are used - something that gives access to all the nice new features?

> Another point, do you it is possible to control the colormap through octave ?
> I think about something like 
> 	kcolormap("colormap_string");

Ideally, eventually, an octave would want to be able to e.g. generate
nice postscript output from kmatplot without ever touching his mouse, or
the kmatplot app for that matter: while one of kmatplot's design
features is its "interactiveness", an octave user would often want to
write a script that generates graph output. And if he changes something
in this script, he(/she) wants to regenerate all the output without
intervention...

> But perhaps it already exists and I didn't have read correctly the doc (RTFM)?

Is there a doc to read that I do not know about? On the topic of docs,
does octave have some nice docs (I'm sure it does...) on writing
extensions, e.g. the kmatplot octave functions? (Depending on how my
holiday looks - depending on what work I'm given at my holiday job - I'd
like to play with octave/kmatplot coding a bit.)

Thanks,
Hugo van der Merwe