• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Filing of User Presets - files vs. builtin
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Filing of User Presets - files vs. builtin


  • Subject: Re: Filing of User Presets - files vs. builtin
  • From: Chris Reed <email@hidden>
  • Date: Fri, 25 Oct 2002 15:40:04 -0500

On Friday, October 25, 2002, at 03:17 pm, email@hidden wrote:

Hi Kurt,

I haven't been following it either, and wouldn't recommend putting such files in the preferences folder (since as you pointed out, they aren't the same). Perhaps in a presets folder within the components folder?

In any case, my only thought based on just about no reading of the thread was that if it's a plist name it a .plist. If it's a preset file name it a .preset file :) That's what file extensions are for.


Exactly :) If it's a preset, name it .preset. The actual format is irrelevant except to us programmers. To the user, it's a preset file. The can't do anything with the file except use it as a preset for whatever AU it's for.

And if they're going to be managing the presets themselves on their drive, I certainly think it makes sense to have the extension identify the file as a preset rather than one of the (as Kurt said) 5000 other plist files on their drive.

Most cases of files with a .plist extension are where the user is not expected to be touching or organising the file(s) themselves.

Plus, Kurt's pointing out of the icon and app linking is pretty important, I think. The icon would be used as another indication to the user exactly what kind of file they're dealing with.

Cheers
-chris



I haven't really been following this discussion closely, but this seems like a really bad idea. .plist is TOO general. It's already in use in a number of completely different contexts (in the persistent storage for CFPreferences, and inside app and bundle wrappers, just for starters). There are already more than 5000 .plist files on my machine, and none of them are AU presets.

A specialized extension would also allow icons to be assigned to preset files, and for the usual linking of files to applications to happen.

Also, in Open dialogs, it's much easier and MUCH faster to filter by file type/extension than to open and read every single file in a directory.

--
Kurt Revis
email@hidden
_______________________________________________
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.
_______________________________________________
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.

  • Prev by Date: Re: AudioUnit ~ AUBase
  • Next by Date: Re: Filing of User Presets - files vs. builtin
  • Previous by thread: Re: Filing of User Presets - files vs. builtin
  • Next by thread: Re: Filing of User Presets - files vs. builtin
  • Index(es):
    • Date
    • Thread