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: Carsten Gehle <email@hidden>
- Date: Fri, 25 Oct 2002 22:43:46 +0200
Hi John,
Using .plist is a standard file extension and would therefore be more
preferable to me.
Well, .plist defines the format of the file, but it does not say
anything about the content. A extension is used to tell the user (and
the application) something about the type of content, not about its
formal format.
Plus, it would be easily openable in Property List Editor which would
be great for development.
Hm, the primary content is stored in the 'data' member which is not
editable with Property List Editor in a proper way.
Plus, if it is a plist, why not show it in the extension, that's what
it's for ;)
A plist is a meta file format (well supported by CoreFoundation and
Cocoa) which does not define anything about the content (Theoretically
any file could be represented as a plist, which would make the file
extensions completely obsolete.). Plists are usually used within file
wrappers (where the file wrapper and the name and location of the plist
declare the contents), or if files are used and edited by different
applications (like application preferences and 'defaults').
Beside extensibility and type checking, the advantage of a plist is
that a user can edit the content of a file, or even setup the file,
manually (eg .eomodel). Concerning AUs, for me it would not make much
sense to change the manufacturer, but not to be able to edit the
parameters. Setting up a file is completely impossible for a user. Even
if AUs states are stored as plists, .plist is not the appropriate file
extension in my opinion. Of course it is possible, though.
Carsten
_______________________________________________
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.