[Mageia-dev] GNOME plans
molch.b at googlemail.com
Mon Jun 4 21:07:33 CEST 2012
2012/6/4 Olav Vitters <olav at vitters.nl>:
> On Mon, Jun 04, 2012 at 08:17:39PM +0200, Wolfgang Bornath wrote:
>> 2012/6/4 Olav Vitters <olav at vitters.nl>:
>> > On Mon, Jun 04, 2012 at 05:51:11PM +0200, Wolfgang Bornath wrote:
>> Leaving out the crap about "change your wording" and whatever.
>> BTW: Pls, calm down a bit, I am quite amazed how emotional you react
>> to this. It's software, not human rights.
> I indeed get annoyed if words such as "crap" are used in discussions.
Yes, me too when someone starts with compalining about my wording.
> Now you've seem to think I'm suggesting that every desktop implements
> their on tool. But that is not what I've suggested.
No, you suggest to implement everything into one desktop's tool.
> Two things:
> - One thing that is shared across distributions
> - Another thing implemented in System Settings
> These are two separate things. This does NOT require a XFCE "system
> settings" tool, as it would be covered by the other tool. If you have
> *one* tool that is shared across distributions, then there must be
> standards to deal with the differences. Standards that can be used by
> the (GNOME) System Settings, more or less duplicating what the other
> tool does. Another possibility that more things are agreed upon between
> distributions, which can then be implemented in System Settings, but is
> still handled by various distro specific tools (MCC, etc) as well.
Yes, perfect. That's the situation we almost have:
- Desktops have the tools for their own settings (window behavior,
themes, behavior of their own applications, etc.). These are the same
no matter which distribution you are using (if the distribution do not
change too much when inplementing the desktop).
Now all we need is a selection of tools such as MCC or YaST or
whatever you may call it for all distributions to do the system
settings (hardware, security features, whatever there is in MCC or
YaST). Of course there may be difficulties because of different
package managements but the graphical tools for software management
should not be too hard to "unite".
Then we are at the point you are heading at, no? As much uniformity as
More information about the Mageia-dev