[Gvsig_english] saving project storing relative path names to layer sources

[Chris Puttick]

IMNSHO file paths referenced in applications should never be absolute, because they can't be. Even if you stick within Windows, you are making the poor assumption that the application will only ever be one computer on one version of Windows, or all organisations have network shares configured the same way (and still use network shares rather than repositories). And good applications (read "applications I permit organisations I manage to use" ;) ), like gvSIG, do not only work on Windows, and it is only on Windows that the silly concept of drive letters even exists...

Why would you use absolute file paths?

Chris

Chris Puttick
CIO
Oxford Archaeology: Exploring the Human Journey
Direct: +44 (0)1865 263 818
Switchboard: +44 (0)1865 263 800
Mobile: +44 (0)7917 058 568
http://thehumanjourney.net

----- Original Message -----
From: "Sergio Clark" <sergio.clark at iver.es>
To: "Users and Developers mailing list" <gvsig_internacional at runas.cap.gva.es>
Sent: 02 January 2008 11:32:14 o'clock (GMT) Europe/London
Subject: Re: [Gvsig_english] saving project storing relative path names to layer	sources

Hello Ernesto,

Yes, that is a good idea. We've been discussing about it recently, and 
we're looking for the best solution. Maybe introduce a checkbox with the 
option Absolute or Relative Path when creating a project, in order to 
solve this problem of portability on different workstations.

For the moment (it's not the same but also helps the users ;-)) it has 
been implemented the option for choosing a new path when gvSIG doesn't 
find the original path of a layer, because layer has been moved or we're 
working in a different workstation. With this, users could see, layer by 
layer, which have not been found and introduce the correct new path. 
This new option is implemented for gvSIG future version 1.2.

Regards! And thanks for your suggestion.

Sergio.

-- 

Sergio Clark
Equipo gvSIG
IVER T.I., S.A.
www.iver.es
www.gvsig.com




ernesto sferlazza escribió:
> Hi all
> Since I've created several replicas of a geographic archive, having 
> the same directory tree schema, on different workstations or groups of 
> workstations operating on different Local Area Networks not connected 
> among them, I think it would be very useful to save projects with 
> "store relative path names to data sources" option instead of the 
> defaul absolute path available in GVSIG.
> In this way I could distribute easily updated versions of a project to 
> all users, without the need of customization of *gvp file (changing, 
> for example, the path from " C:\SIT_provinciaAG \TRASPORTI\STRADE" to 
> " F:\archivioSIT \TRASPORTI\STRADE") using a text editor.
> I have tried, also, to change with a text editor the full path to 
> relative path subtituting "..\" instead of the archive root path (in 
> the example " ..\ " instead of " C:\SIT_provinciaAG \ ", but it didn't 
> work as I believed.
>  
> Best regards
>  
> ing. Ernesto Sferlazza
> responsabile Unità Organizzativa Sistema Informativo Territoriale
> della Provincia regionale di Agrigento
> piazza Aldo Moro, 1 - 92100 AGRIGENTO
> tel 0922 401935
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at runas.cap.gva.es
> http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional
>   



Este mensaje y sus archivos son confidenciales. No está permitida su reproducción o distribución sin la autorización expresa de "IVER Tecnologías de la Información". Si usted no es el destinatario previsto, queda desautorizado cualquier uso, acceso o copia de este mensaje. Si ha recibido este mensaje por error, por favor bórrelo e infórmenos por esta misma vía.


_______________________________________________
Gvsig_internacional mailing list
Gvsig_internacional at runas.cap.gva.es
http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional




------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.