[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: graphics-branch in CVS
From: |
Shai Ayal |
Subject: |
Re: graphics-branch in CVS |
Date: |
Fri, 8 Dec 2006 21:34:18 +0200 |
On 12/8/06, John W. Eaton <address@hidden> wrote:
On 8-Dec-2006, Shai Ayal wrote:
| Octplot does have a very large portion of the plotting functions
| converted to use handle graphics, so you could use them
It would be good if we did not duplicate effort here. It seems that
we should be able to come up with some common versions. To start
with, anything that can be defined in terms of commands like get, set,
line, axis, etc. could be shared. Where should the primary version of
these functions live, in the Octave CVS archive or the OctPlot SVN
archive? Also, we would need to merge any functions that are already
in both projects so that we make sure to not lose features. I would
also ask that they mostly conform to Octave coding convections.
I have no problem with putting these in the octplot svn -- as I said I
am very promiscuous in granting write access to svn. However, since
these are going to be an integral part of octave, it seems they should
be in octave cvs -- everyone who downloads octplot will also download
octave, however the converse is not true (at least yet ...). My only
worry is that octaves higher standards for code quality will clash
with my tendency for quick releases.
As for coding conventions -- I do not know what they are for m-files,
can you please refer me to something here? The functions are quite
complete feature-wise, and I tried to conform to the RFC by Bill.
Probably argument checking is not perfect, but all the high level
functions -- (e.g. plot, contour etc ...) should be totally portable,
and in fact they should also run in matlab (although I cannot check
since I don't have matlab).
Shai
- Re: graphics-branch in CVS, (continued)
Re: graphics-branch in CVS, David Bateman, 2006/12/08
Re: graphics-branch in CVS, Shai Ayal, 2006/12/08
Re: graphics-branch in CVS, Joe Koski, 2006/12/08