[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Default preferences (was Re: Plans for ahead)
From: |
Gregory Casamento |
Subject: |
Re: Default preferences (was Re: Plans for ahead) |
Date: |
Sun, 29 Nov 2015 02:02:58 -0500 |
German, please see my reply to you on the other thread. Thanks.
On Sun, Nov 29, 2015 at 1:38 AM, Germán Arias <germanandre@gmx.es> wrote:
> Hi,
>
> El sáb, 28-11-2015 a las 16:25 +0100, Riccardo Mottola escribió:
>> Hi,
>>
>> David Chisnall wrote:
>> > I agree. The FreeBSD GNUstep packages include a lot of things, but you
>> > need to do a lot of tinkering to make them integrate even vaguely with
>> > typical environments. For the ones that we use in the lab, I’ve
>> > configured a more modern looking theme[1] and the in-window menus. With
>> > this, the apps still look fairly distinctive, but work quite well and
>> > people don’t complain.
>>
>> I absolutely want "our" menus, they are distinctive and useful and if I
>> were to make a reference distribution, I'd want to retain that.
>>
>> You have the opposite problem, you want to deploy a certain GS
>> application into a non-GS environment.
>> I know the pain, I have exactly the same need!
>>
>> I have my app, I have an in-window menu theme (in this case needed
>> because you are the foreign thing to fit into Windows or GNOME). But
>> then still every single user needs to "set" the theme for himself.
>>
>> This is the problem I often referred to, where I want to be able to
>> "set" a default preference for a user. Or to have certain preferences
>> pre-set inside a plist. A way so that once installed an pp sets some
>> defaults to itself. System wide defaults?
>> When installing with a package one could do perhaps a post-installation
>> script, but that is not my case.
>>
>> I think this is the opposite of the original topic, but still very
>> useful to solve.
>>
>> Riccardo
>>
>
> But this is possible using GlobalDefaults subdirectory or
> GlobalDefaults.plist as described here:
>
> http://www.gnustep.org/resources/documentation/Developer/Base/Reference/index.html
>
> The only case when this doesn't works for me, is for a binary package of
> gnustep itself (for development). In this case I need provide a
> GNUstep.conf with paths for libraries and headers. And it seems that
> cause conflicts with GlobalDefaults when user source GNUstep.sh. So he
> should run SystemPreferences and make the necessary changes. Or maybe
> I'm doing something wrong.
>
> Germán
>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
--
Gregory Casamento
GNUstep Lead Developer / OLC, Principal Consultant
http://www.gnustep.org - http://heronsperch.blogspot.com
http://ind.ie/phoenix/
- Re: Plans for ahead, (continued)
- Re: Plans for ahead, Alessandro Sangiuliano, 2015/11/30
- Re: Plans for ahead, Ivan Vučica, 2015/11/30
- Re: Plans for ahead, Robert Slover, 2015/11/30
- Re: Plans for ahead, Matt Rice, 2015/11/30
- Re: Plans for ahead, Robert Slover, 2015/11/30
- Re: Plans for ahead, Germán Arias, 2015/11/30
- Re: Plans for ahead, Liam Proven, 2015/11/30
- Re: Plans for ahead, richard, 2015/11/29
- Re: Plans for ahead, Adam S, 2015/11/29
- Default preferences (was Re: Plans for ahead), Germán Arias, 2015/11/29
- Re: Default preferences (was Re: Plans for ahead),
Gregory Casamento <=
- Re: Plans for ahead, Riccardo Mottola, 2015/11/27
- Re: Plans for ahead, Riccardo Mottola, 2015/11/27