Re: Feature proposal: combined system status menu

[Leslie S Satenstein <lsatenstein yahoo com>]

Giovanni
I second your message. There are a few things in Gnome3.8 that need to be standard and not tweaked.
a) User should be able to reset Frequent, or at least purge entries therein.  I do it by deleting the users .hidden files.  But that is not the way.
b) In testing Gnome3.8, I ignore Frequent, and only use ALL.  (It saves me 1 mouse click, and come  tendonitus.). I scroll once, instead of searchng FREQUENT, and then researching ALL.

When we add desktop applications (say another two dozen) to the system, scrolling the ALL section means via mouse, requires a lot of activity and searching to find the program we want.  

C) The categories (programming, system, applications, as was in 3.6, was a great way to reduce mouse clicking.  Developers have to consider how fatiguing it is to use the mouse with Gnome3.x    (Yes there are tweaks, but I can;t do an install of multiple desktops if I have to manually install tweaks for each one).

d) In a future release..  Please allow us to create our own tags, and use them to search against them.   .

e) Gnome 3.8 and the split window feature (extreme slide left or slide right) is great. Congratulations to the developer(s).

Regards

 Leslie

Mr. Leslie Satenstein
50 years in Information Technology and going strong.
Yesterday was a good day, today is a better day,
and tomorrow will be even better.

mailto:lsatenstein yahoo com
alternative: leslie satenstein gmail com
SENT FROM MY OPEN SOURCE LINUX SYSTEM.

--- On Mon, 4/22/13, Allan Day <allanpday gmail com> wrote:

From: Allan Day <allanpday gmail com>
Subject: Re: Feature proposal: combined system status menu
To: "Giovanni Campagna" <scampa giovanni gmail com>
Cc: "desktop-devel-list" <desktop-devel-list gnome org>
Date: Monday, April 22, 2013, 2:18 PM

Hey Giovanni!

Giovanni Campagna <scampa giovanni gmail com> wrote:
> As one of the implementors of the current status icons, and current
> developer of gnome-shell, I can tell it's a small can of worms, but that's
> not what this is about.
> Rather, what I'd like to point out is that, in my opinion, this needs more
> thinking through before going straight to shipping.
> I mean, I trust the design team and I value your experience in the field,
> but this is another radical change, and it's quite different from our
> competitors.
> Unfortunately, we don't have the benefit of two years of betas, so if we
> implement and deliver this 3.10, there is a risk of an impendance mismatch
> between what's expected from the designs and theory behind them, and how the
> user effectively react. Which would bring even more negative publicity to
> GNOME.
> This is generally a problem of every fast releasing project with little man
> power, so it affected many of the features in 3.8 and before, but at least
> at time we had the validation of other systems doing the same.
> To me, a reasonable compromise (yet to decide if technically possible) would
> be to have a "feature branch", that is not merged in master until after it's
> thoroughly user tested. And that possibly gets punted to 3.12 or never, if
> it turns out to be a bad idea.

Yeah, I'm aware that we need to tread carefully. I've actually spent
quite a while sitting on these mockups, revisiting them and
challenging them with different scenarios - you will also notice that
they are pretty detailed.

So yes, I'm in agreement with you about pushing this prematurely.
Working in a branch seems like it could be a good solution.

Allan
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list