dolfin team mailing list archive

[Ola Skavhaug <skavhaug@xxxxxxxxx>]

On Sun, Mar 22, 2009 at 9:49 PM, Johan Hake <hake@xxxxxxxxx> wrote:
> Hello!
>
> Now that we have removed the read/write Function from/to file in the c++
> interface we have to change the python interface too. I haven't done this
> yet.
>
> But before I do this I wonder if we _should_ add some logic in the python
> interface that allow the functionality we previously had, i.e., writing and
> reading Function to and from a file directly?
>
> We could perhaps extend the <</>> operator in the c++ wrapper so an xml file
> with the vector, mesh and the FiniteElement signature will be saved in. Then
> in python we can jit compile the FE, when reading the file. We should
> probably have one constructor taking only the xml file but also one taking an
> optional mesh argument, preventing the problems with duplications of meshes.
>
> Would this be desirable? I know Ola have made some thoughts about this.

I have no strong opinions here. Just stating the obvious that the C++
and Python interfaces will be different. The discussion should be if
the main developers like that. The new FunctionPlotData class takes
care of saving solutions to file for plotting, so then I'm happy.

Ola

>
> Johan
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev
>



-- 
Ola Skavhaug