[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changes I've been thinking of...

From: David Chisnall
Subject: Re: Changes I've been thinking of...
Date: Wed, 7 Oct 2009 23:00:28 +0100

On 7 Oct 2009, at 22:38, Matt Rice wrote:

On Wed, Oct 7, 2009 at 2:28 PM, Stef Bidi <address@hidden> wrote:


13.0) there's not way for me
to set a default, "preferred" theme--which is what the GUI toolkits above allow you to do--there is just no way for me to do that. I know it's been brought up a few times in the past, and if I remember correctly it's because of the way NSUserDefaults is setup, so (again, in my opinion) that's where
the problem lies.

I believe you are mistaken, NSUserDefaults handles global settings
fine, you just need to add the default to the NSGlobalDomain,

Unless I have missed something, NSGlobalDomain is a per-user thing. There is no sensible way of setting a default value for a user default globally. Apps can do this via the standard APIs, but there is no way for packagers to provide a default value for a default. For example, we can put Camaelon and Nesedah in a package, but there is no way to make it the default theme for any users who have not selected a theme as part of the package installation. This question has been asked on the list before and no one replied with a way, so I assume it is still impossible.

It would be nice to have a standard directory for plists which are merged together to provide the default user default values. I looked at doing this a while ago, but it required implementing whiteout in the per-user defaults (so you could delete a default that exists in this directory).

This is something else that we need to address. The OpenStep style of distribution is to provide drag and drop application bundles, which are great for single-user system but not ideal for multi-user systems like a typical *BSD or Linux distribution. There are probably quite a few things that we could do to make it easier to package GNUstep and GNUstep apps / frameworks that we miss because we all build from source, which would help a lot with adoption.


-- Sent from my Apple II

reply via email to

[Prev in Thread] Current Thread [Next in Thread]