[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: graphics-branch in CVS
From: |
John W. Eaton |
Subject: |
Re: graphics-branch in CVS |
Date: |
Fri, 8 Dec 2006 11:39:01 -0500 |
On 8-Dec-2006, Shai Ayal wrote:
| On 12/7/06, John W. Eaton <address@hidden> wrote:
| > * It is slow. Some of this can probably be fixed by translating the
| > core code that deals with the list of graphics handles to C++. It
| > may also be necessary to convert the code that processes the plot
| > data structure and interacts with gnuplot.
|
| Also, keeping all the data in octave ans sending it to gnuplot each
| time could be very time consuming -- when plotting large datasets it
| would be very annoying. I think for the future plotting backend some
| sort of shared memory scheme should be implemented, although I have no
| idea how to do it.
Yes, I know that there are problems like this. Please remember that I
prefaced the list of limitations by saying that I think of this code
as an intermediate solution to graphics problems in Octave. I don't
expect that it will be the ultimate solution, but it is a step in that
direction.
jwe
- 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