Philip,

On 15 Nov 2010, at 21:09, Philip Nienhuis wrote:

> Oh I didn't know. Thank you for this info.
> I suppose Levente and I just followed Martin Helm's suggestion (in the 
> maintainers-octave ML) to put them in IO.
> Googling around for vtk I got the impression that vtk is more related to 
> graphics output than just plain file I/O but then again not so closely as to 
> put the scripts in the plot pkg.
> 
> So, if there's already a better home for <whatever>vtk in the fpl pkg I think 
> it's a good idea to put them there.
> 
> I'll wipe them from io svn (I uploaded them just yesterday).

I didn't mean to say you should remove them, maybe io IS the right place for 
functions that write vtk files?
what I meant is that, given that we have many different functions that save to 
different vtk file formats, maybe we should 
chose one single package where they all can be put together.

I see different possible solutions and would be interested in hearing somments 
from others

solution 1) 
putting all vtk-file related functions in fpl which is a package meant to be 
used for allowing data visualization with external programs

solution 2)
as many functions to output in third party file formats are in 'io' maybe the 
vtk functions should also go there

solution 3)
'fpl' is composed of 3 different sets of functions: 
[a] functions to output data in external file formats (.vtu and .dx)
[b] wrappers for controlling opendx visualization from within octave
[c] wrappers that produce plots in octave's own plotting system with a syntax 
compatible to matlab's pde-toolbox (pdeplot, pdemesh)
so maybe we could get rid of 'fpl' by moving [a] into 'io' removing [b] (as 
opendx is now obsolete and unmaintained) and moving [c] into 'bim' which is a 
package similar to pdetool


> Nevertheless, I think (some/most/all of) my remarks about style and error 
> catching still hold (especially error catching as unwary users may have undue 
> trouble figuring out exactly what went wrong when errors occur).

I also think your comments did make sense

> Philip
c.
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to