[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-active
Subject:    [Bug 287228] onMeeGo: while the device is plugedIn, the battery
From:       Thomas Pfeiffer <colomar () autistici ! org>
Date:       2011-11-22 11:41:20
Message-ID: E1RSoj2-0000z2-F6 () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=287228





--- Comment #8 from Thomas Pfeiffer <colomar autistici org>  2011-11-22 11:41:20 ---

> My first ideas are scribbled in those two wireframes:
> http://share.basyskom.com/contour/UIDesign/Locking_Hibernate_V2.jpg
> http://share.basyskom.com/contour/UIDesign/Locking_Hibernate.jpg

Well that's pretty much like the traditional shutdown plasmoid with PA look &
feel, isn't it?
(
http://ubuntu.paslah.com/wp-content/uploads/2011/08/The-desktop-menu-Leave.png
)

> Interactions would be:
> - short press on hw power button: automatic locked screen, every app still
> running, no energy saving

Makes sense to me, as you often want to quickly lock the screen because you
need to carry the device around for a few meters.

> - long press on hw power button: hard shut down (we have that currently), maybe
> data loss

That's a hardware function anyway, correct?

> - short tab on power icon in Plasma Active GUI (see wireframe
> Locking_Hibernate.jpg, icon on the left upper corner) brings up an overlay with
> the following options:
>     - Lock: Brings Lock Screen up, system doesnt react on touch anymore, apps
> are still running (so user can still listen to music for example)
>     - Sleep: Aggressive powermode, minimal energy consumption, short wake up
> time (under 3s)
>     - Turn off: shuts the device down, but asks for open dialogs, save dialogs
> etc, without data loss

What about hibernate? It has the advantage of no data loss and faster boot-up
time. The advantage of shutdown though is that if allows for a "clean start".

> - I was also thinking about other options, see Locking_Hibernate_V2.jpg with
> sleep, restart and turnoff; but in my opinion restart is only a needed option
> for testers and developers, not for endusers

In a perfect world, that's true. But I don't think we can expect there won't be
bugs that affect the system so badly that even end users will want to reboot
their device. This may be a little more hidden than the other options since it
is only for cases of "emergency", but I'm not convinced that no end user will
ever need it.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
[prev in list] [next in list] [prev in thread] [next in thread]