Hmmm... not a bad idea.  I'll put the Exodus documentation over into
the doc tree soon.

Derek

On Nov 24, 2007 4:32 AM, Martin Lüthi <[EMAIL PROTECTED]> wrote:
> Hi
>
> Libmesh supports a wide variety of data formats. For some formats the
> documentation is easily accessible, but for some (e.g. UNV) one has to
> hunt down some description of the file format.  I think that it should
> be mandatory to put the file definitions into the the doc tree (as has
> been done for the xdr family), or, if that is not possible for
> copyright reasons, to put links (URLs) in the header files.
>
> WDYT
>
> Best, Martin
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Libmesh-devel mailing list
> Libmesh-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to