octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #52812] Graphic object properties should appea


From: Rik
Subject: [Octave-bug-tracker] [bug #52812] Graphic object properties should appear in their own index in manual
Date: Sun, 7 Jan 2018 10:40:22 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #2, bug #52812 (project octave):

@Dan: There are two "@defindex op" declarations because there are two separate
pieces of documentation being produced.  The documentation in doc/liboctave is
just for liboctave, i.e, if you just want to link in the octave computational
library to your C/C++ programs.  I'm pretty sure that gets used very, very
infrequently, but it is there.

There isn't any need to document the graphics properties in liboctave because
the graphics system is part of the interpreter.

The graphics properties are neatly organized by graphics object, but to get
quickly from the help for the figure object to the list of figure properties
requires a link.  That's why I filed bug #52816 (All graphic objects should
have an XREF to the description of their properties).

The list of individual properties should be in some kind of index, as it is
now.  To go directly to a particular object's property use doc() as in


doc "figure colormap"
doc "axes children"




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52812>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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