On Wed, 2004-07-21 at 13:58, Alan Horkan wrote:
Then your Gnome must be very different from mine.
I just right-click and pick "open with" and choose the app.
Try opening it with an application not already included on your 'open with' list. It is just messy and unpleasant.
But you should only have to do it once -- and how many end-users will be editing these files?
Actually, for me there *is* a benefit today. I can get them to open in Emacs instead of Mozilla. I'd want to edit them, not view them as raw XML.
does that not just mean that the having Mozilla as your defualt instead of Emacs what is wrong?
Well, there we also get into issues of "open" (view) versus "edit" being separate verbs (or not) in the desktop environment as well..
Oh, and if I create a new file with XML content but an unknown extension, it opens it with the default text editor. Sounds like about what I'd want it to do for general users.
pretty close yeah.
Further to your point about ini files, surely there is an existing XML based format for configuration files could be used rather than needing something overly inkscape specific?
It's probably worth looking at other configuration formats, but I think we're better of using a specialized schema rather than trying to shoehorn in something _too_ generic (like OS X proplists).
By the way, while I think it's a good idea to have extension preferences in separate XML files from the main preferences, I would like to preserve a single namespace for preferences as viewed from the actual preferences API.
That might involve something like "mounting" a file into the namespace (but that should be handled automatically as part of extension registration/unregistration).
-mental