----------------------------------------
> Date: Fri, 1 Oct 2010 21:29:15 +0200
> Subject: Re: [Viking-devel] [PATCH] Make more portable .vik file, as don't
> save the map cache directory if it's the map cache default directory.
> From: guilhem.bonnefi...@gmail.com
> To: rw_nor...@hotmail.com
> CC: viking-de...@lists.sf.net
>
> Patch applied.
>
> Nevertheless, such solution creates .vik file that does not support a
> change of the preference.
> Here is a scenario: I save a file, change the preference, and reopen
> the saved file...
Ah yes you're right, I didn't think about that.
I was hoping to try to make the .vik file a bit portable, but perhaps that can
not be done in a such a simple way as I was hoping.
Normally I think other software that deals with references to other files are
often relative references.
Obviously absolute filename references are not cross platform.
There is an open SF#2998555 about this (albeit more for waypoint image
references).
I have a partial working solution for SF#2998555, but that ATM only addresses
the waypoint images.
Other places that use file references:
.DEMs
.GeoRefs
.Map Cache (as this patch was about)
Further I was then thinking of adding an advanced preference to say 'save in
either relative or absolute mode', which only affects the saving.
Reading files in is simple, as it can tell been '/absolute/file' and
'relative/file' (in fact I think the OS's open function does that automatically
for you)
This is very much a 1.0+ change.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
