GNOME3 feature page - updated scoped and comments

[Bastien Nocera]

On Wed, 2011-02-09 at 11:18 +0000, "Jóhann B. Guðmundsson" wrote:
> On 02/08/2011 09:37 PM, James Laska wrote: 
> > = Comments & Discussion =
> > Given that GNOME 3 offers a *dramatically* different user experience
> > than GNOME 2.X, there are going to be plenty of users who are
> > surprised/disrupted by the changes.  As a result, we wanted to start
> > compiling common questions/workarounds/workflows that have come up so
> > far.  I anticipate referencing these a lot on irc/lists.  Perhaps, over
> > time these migrate into release notes.
> 
> We need to get this list going and keep tabs on bugs filed against
> that design decisions and preferable point to upstream
> bugs/discussion(s) as Bastien did in respond to me in another thread
> on this list since I hit yet another case what I call a regression/bug
> but another might call works as designed.
> 
> We had a shitty weather last night which was perfect for me to just
> throw myself in the couch in the living room reading a ebook over a
> warm cup of coffee before you hit the sack well that did not turn out
> so well I spent most of the time battling "power saving" features
> since I was running the laptop on battery on my couch in my living
> room. 
> 
> No matter what I did ( setting the brightness to max ) after I period
> of time I either had a screen lock or the display decided to dim it
> self again which by the way to not seem to be consistent to behaviour
> I set it to and going through the power settings I notice that for
> some reasons the ui designers have decide to remove the option "Never"
> and in the end I accepted defeat ( or achieved victory over power
> saving depending how you look at it ) and unplug one of the lamps in
> the living room and plug my adapter in to work around "Power saving"
> behaviour.  
> 
> These four bugs I encounter as in three code bugs one design bug or
> are these not bugs and are *working* as designed?
> 
> 1. 
> 
> The screen lock taking place which did not be consistent to what
> settings I had in power settings. 

The screen lock also did not remember its state after restarting the
panel I guess. I hooked up this code yesterday upstream.

> 2. 
> 
> The display deciding to dim it self after a period of time that did
> not seem consistent to what I had set to in the power settings. 

That's a bug. Although you probably mean the "Screen" settings, because
there's no such setting in the power settings.

> 3. 
> 
> The display deciding to dim it self after an reset the display
> brightness setttings after I manually set it ( happens regardless if I
> used a key compo to increase it or I did so through application ).  
> 
> 4.
> 
> Usability regression or a design bugs as I call them the removal of
> "Never" as an option and be stuck with one hour.

This is not a bug though.

<snip>
> Note that I have not filed a single one of those bug(s) I have
> mentioned since I'm not sure these are bugs at all or working as
> designed. . .

If you're reading an e-book in fullscreen, your e-book reader should
probably inhibit the idle timer so that 1) your screen doesn't dim 2)
your screen doesn't lock when you're reading an e-book.

That would solve all your problems above. For the rest, be patient and
wait for the recently written code to get downstream.

Cheers