Re: Filing of User Presets - files vs. builtin
Re: Filing of User Presets - files vs. builtin
- Subject: Re: Filing of User Presets - files vs. builtin
- From: Robert Grant <email@hidden>
- Date: Fri, 25 Oct 2002 12:24:48 -0400
Reading this again I've got a couple more comments:
On Friday, October 25, 2002, at 10:09 AM, Art Gillespie wrote:
I think someone's got their head around this the wrong way. Presets
are user documents, period. These options of 'where to store them'
indicate that they're being thought of as components, which they most
certainly are NOT. I don't want Project Builder saving my source files
in my preferences directory (or even making decisions about the layout
of my source tree) and I don't want Word bundling all my .doc's in a
single file in my Preferences directory.
I'm sympathetic to what you're saying but I'm just troubled about
whether
we can give the user the best interface without a stricter scheme. If
all the
presets are named xxxx.plist then it will appear in any file selection
box that
the user can load any preset they see, when in fact there's only a
limited subset.
Fine for the experienced user, perhaps, but potentially confusing as
hell for a novice.
Unlike you I don't think of presets as documents, they're not big
enough to
warrant that overhead. I think presets are more like Mail.app's Rules
or Microsoft
Word's Macros: small useful customizations that shouldn't be a big
organizational
headache, and shouldn't get lost!
If we could just differentiate the bloody things!
Robert.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.