[Gvsig_english] Persistant xml code from prior sessions in .gvp files

[georgsedlmeir]

Dear list,
in the course of switching from ArcView to gvSIG we regularly need to edit
.gvp files directly, i.e. to change path names.
It often requires more time than desired to step through the xml code
because the .gvp contains tags originating from prior gvSIG sessions, like
descriptions of layers that are not part of the current project anymore, and
those "historic" parts inflate the xml considerably and make it less
readable. Obviously xml wasn't primarily invented to be read by human eyes
but sometimes there are odd requirements like ours. 
Are there reasons why the code from preceding sessions has to remain in the
xml, or would it be a big effort to modify the way the xml is written,
trimming the corresponding parts from it when a layer is deleted?

Best regards,
Georg

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Persistant-xml-code-from-prior-sessions-in-gvp-files-tp6087692p6087692.html
Sent from the gvSIG users mailing list archive at Nabble.com.