On Sun, 2005-08-21 at 21:44 -0700, Jon Phillips wrote:
I believe that the code is currently ready to be preliminarily checked into Inkscape CVS. The main question I have about that right now is how to deal with the configuration file. The script searches for the config file both in the Inkscape extensions directory and in the ".inkscape" directory in the user's home dir (both can be used simultaneously... conflicting settings favor the user file). The extensions dir seems like a pretty dumb place to put a configuration file; is there a better location I should use?
Has anyone answered this yet? I'm not currently sure, but I agree with you that there might be a better place for conf files for extensions...I can see as more and more extensions get added that this folder is going to grow. Maybe a better strategy is to have folders for each extension in the extensions folder, and then inside that folder could be any type of file related to the extension. I think this is how plugins are handled on Photoshop and Illustrator.
The problem with the user folder is that its per user; you'd have to create one for every Inkscape user on the system, and it seems more logical to make the main config file, at least, be system wide.
Right I agree, and its good to have the user config file override the system-wide one...agree!
I don't know if this is the 'the answer', but I think it highlights why we need to start using GConf for configuration settings. It handles all the system/local/schema issues for us, which would remove another decision from our realm and put it where the sysadmin can make one system wide policy.
Tor was porting Evolution (including GConf) to Windows, I haven't been following it though. I was hoping that it would be done for the next major Evolution release.
--Ted