From: vsr Date: Thu, 25 Feb 2010 17:46:07 +0000 (+0000) Subject: Improve documentation for read/write drivers X-Git-Tag: V5_1_main_FINAL~188 X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=40c81fe81389e5f283442f17396d41abc5b4d32b;p=tools%2Fmedcoupling.git Improve documentation for read/write drivers --- diff --git a/doc/doxygen/medmem.dox b/doc/doxygen/medmem.dox index 31d977323..e2e10c2ad 100644 --- a/doc/doxygen/medmem.dox +++ b/doc/doxygen/medmem.dox @@ -32,7 +32,7 @@ As will be seen in section \ref medmem_api, the API consists of very few classes - supports and derived classes : \ref support , - mesh generation tool : \ref meshing , - fields : \ref field , -- drivers for reading and writing in MED, GIBI and VTK files. +- \ref medmem_drivers "drivers for reading and writing" in MED, GIBI and VTK files. All these are detailed in the following sections. The C++ formalism will be used for the description in these sections. @@ -88,7 +88,8 @@ MEDMEM supports data exchange in following formats: - \b EnSight - reading and writing the mesh and the fields in ASCII and binary formats. - \b PORFLOW - reading the mesh in ASCII format. -Limitation of length of names in GIBI format is overcome by storing names in the string pile. +Limitation of length of names in GIBI format is overcome by storing names in the specific string pile of GIBI file. +This pile is used to map actual long names of the data objects to their shortened representation. \section medmem_api Med Memory API