Re: Design Principles
Re: Design Principles
- Subject: Re: Design Principles
- From: Albion Baucom <email@hidden>
- Date: Fri, 23 Jul 2004 14:49:00 -0700 (PDT)
On Fri, 23 Jul 2004, Pandaa wrote:
>
If you want a mechanism of having the preference change be applied
>
alternatively to *one* document *or* to all documents, I would suggest
>
separating the preferences for which that makes sense from the general
>
preferences and show them in a sheet for every document instead of
>
introducing a concept of scope to your preference panel.
Possible, but currently I am replicating a Windows based application, and
my first job is to make a cocoa copy of it verbatim. Then I can branch
out. I thought of that early on, but can't because of the design
restrictions currently.
>
Is there a special reason you are not using NSUserDefaults to store
>
your preferences? If not, I suggest storing your preferences directly
>
in the NSUserDefaults standardUserDefaults. That way you won't need
>
your Preferences object, and any object that needs to read preference
>
settings can do so easily.
No, there isn't. This sounds better. User specific preferences are much
slicker. I had overlooked this. Thanks, this is key.
>
If it only needs to talk to the customview to broadcast preference
>
changes, use notifications. It is probably more elegant to use
>
notifications. Let your preference GUI send notifications when a
>
preference is changed, and have any object in your application that is
>
affected by the preference register for said notifications.
Cool, yes, this looks better. I was looking at a cascade of method calls
to get through the heirarchy. That seemed clusmy, this sounds more
elegant.
Thanks very much!
Albion
Albion E. Baucom
http://rna.ucsc.edu/albion
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.