On Thu, 12 Feb 2004, Ted Gould wrote:
On Thu, 2004-02-12 at 00:22, Bryce Harrington wrote:
Distribution / Packaging Files
Sounds good to me.
Config Files
This sounds like a good thing to do, but I'm curious if it's not a waste of effort if we're going to go to a GConf/registry solution in the future. We get most of this configuration stuff for free from GConf in the unix world (and Windows people don't expect that level of administration ;).
Oh, I didn't know we were going to go to GConf. Are we certain that's the right way to go?
"Share" Collateral
I like this too.
For clipart, I think we definitely want to consider being able to tie in with "external" clipart collections. One way would be to simply put symlinks in the clipart dir to those collections. This way, if the flags package were to install into /usr/share/flags-svg/, we'd just symlink there.
I think it would be better for us to have a configuration item that is the list of directories to look for clipart. This way we could have the same 'global' and 'user' directory, but also any clip-art library on the system directory.
My thinking is that if it is done via a config file, then when the application in question installs itself, it would need to parse and re-write Inkscape's config file, whereas with symlinks no such parsing and editing would be expected.
Possibly similarly for extensions.
I think the above has to happen for extensions.
I think an argument could be made that the tutorials ought to be placed somewhere under the /usr/doc/ or /usr/local/doc/ path, so I'm not 100% certain of having the tutorials located here.
I like having them in share personally. Just because I think that most people are going to access them through the menu item - and thus are an internal function not a documentation one.
That was my thinking as well.
Bryce