Re: [FR-devel] user config files, pathing, etc.

[Laurent Julliard]

Richard Kilmer wrote:

> Hey all,
>
> I ran into a funny problem with the way that properties files are 
> persisted right now into the local USERPROFILE/HOME dir.  I added a 
> path to an additional directory to contain plugins (via the 
> config/properties.yaml file).  The path I defined was relative 
> (../../somepath) and what was amusing was the way that the properties 
> are persisted it created a directory structure in the 
> USERPROFILE/../../somepath (which is BAD).  Anyway, the way in which 
> the current config files are stored was straightforward to implement, 
> but I think leads to potential (or in my case real) problems.  I am 
> reviewing the current strategy, and my recommended change is that we 
> change the user_filename to just keep the @@userdir and the deepest 
> dir in the filespec so:
>
> ./plugins/rubyide_gui/appframe.yaml
> is converted to
> USERPROFILE/freeride/rubyide_gui/appframe.yaml
> or on linux
> HOME/.freeride/rubyide_gui/appframe.yaml
>
> and
>
> ../../myotherplugins/test_plugin/properties.yaml
> is converted to
> USERPROFILE/rubyide/test_plugin/properties.yaml
> or on linux
> HOME/.freeride/test_plugin/properties.yaml

When I made the quick hack to handle user property files I thought of 
the ../.. problem but considered that it would take ages before sbdy 
actually uses it. I was obviously wrong :-))

I think your approach is fair. One of the drawback is that it limits the 
user directory to one level deep but this is probably acceptable for now.

> in addition, i want to add the ability to have access to a modified 
> path through the plugin class so in a plugin wanted to write misc file 
> out it could call plugin.user_filename(filespec) which would call the 
> properties reader to convert.


This one is definitely a yes!

> Thoughts?
>
> Rich
>
>
>
> _______________________________________________
> Freeride-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/freeride-devel