Re: WTF⁈ ShowOnlyIn=GNOME

[Christopher Stone]

On 7/24/07, Jesse Keating <jkeating at redhat.com> wrote:
> On Tue, 24 Jul 2007 18:34:09 -0700
> "Christopher Stone" <chris.stone at gmail.com> wrote:
>
> > Can you please clarify?  How is it any different if a system has one
> > user or one hundred?
>
> I can have a handfull of gnomeusers that only want gnome apps like
> gedit.  I can have a handfull of kde users that only want kde apps like
> kate.  I can have other "power" users that make use of things like
> gnome-menu or the kde equiv to see /all/ items.  I don't want to
> needlessly clutter the gnome user's menus with 10 different editor
> choices, or even 2.  Likewise others.

Yes, and I can have a handfull of kde users that only want gnome apps
like gedit.  I can have a handfull of gnome users that only want kde
apps like kate.

What's the difference?



> > I'm not sure what a "user controlled system" means.
>
> Where the user is the admin and is in control over what applications
> are installed.

So I still don't understand your argument against adding menu items
for installed applications in this case.



> Most often those that install "everything" are the ones that put no
> thought into what they actually want.  They give up and just install
> everything, and then complain when the menus are too cluttered.

Yea, okay.  Let's make life difficult for everyone else so that the
idiots who install every application will no longer complain about
every application showing up in their menus.

This makes a lot of sense.  NOT!



> It's not like we haven't played this game before.  While what we have
> now may have a few bugs, and a few ShowOnlyIn may need to get converted
> to DontShowIn or some such, it's a far sight better than the chaos
> we've had before.  And yes, some tools like gnome-menu should probably
> learn to override/ignore these things and show what it would look like
> on a gnome login.


I see nothing wrong with gnome-menu and/or kde-menu as long as its
able to override ShowOnlyIn.