[Bug 287228] onMeeGo: while the device is plugedIn, the battery symbol vanishes, so that options like sleep cannot be activated

[Lamarque V. Souza]

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





--- Comment #9 from Lamarque V. Souza <lamarque kde org>  2011-11-22 12:21:06 ---
(In reply to comment #7)
> Hm... on the other hand, many icons only appear if something _happens_. So one
> could say "The icon is displayed as long as the battery charges or
> dischagres", which it does not do when it's full.

I think we could change the icon to indicate the battery is fully charged. Some
OS even write
the word "Charged" beside the battery icon.

> But you and Fania do have a point I guess, and most if not all OSes - desktop
> an mobile - I know keep the icon displayed even when the battery is full.

That is what I had thought.

> They might expect it, but do they _look_ for it there? I for example have never
> hibernated my laptop or put it so sleep from the battery icon, as I have a
> dedicated button for that. So okay, long time KDE users will eventually
> remember that possibility after unsuccessfully looking for a leave button, but
> I don't think it's the first place even they will look for it.

Fania and me are working with tablet devices. They usually do not have
dedicated sleep/hibernate buttons. The only button we have is the power button
and as Fania wrote we plan to use it for "screen lock"/"hard shutdown", we need
an alternative for sleep/hibernate/shutdown.

Plasma-device (in plasma-mobile) does not have a main menu button like
plasma-desktop. If it had
we could add the "sleep/hibernate/shutdown" there like Kickoff and Lancelot do.
But I have the feeling that
whoever decided not to add a menu button has reasons for that.

(In reply to comment #8)
> > 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
> )

    Not exactly a plasmoid, it is a plasmified menu. They are similar and share
the same porpose.
We would need to remove the shutdown context menu and increase the menu item's
height to use it in tablets though.
Some days ago Marco Martin also mentioned making the menu themable using QML.
That can take some time though.

> > 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.

    Although suspending to ram (sleep) is more recomended  in that situation
than simply locking the
screen if your device uses rotational media (traditional hard disk, DVD
reader). The lock screen is usefull when you want to leave the computer turned
on and go somewhere without it.

> > - long press on hw power button: hard shut down (we have that currently), maybe
> > data loss
> 
> That's a hardware function anyway, correct?

    Yes.

> 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".

    It can be added easily. I implementated the first version of that dialog.

> 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.

There is always the "shutdown and then turn on" alternative. If the system is
so badly affected then the only alternative is the hard shutdown anyway (long
power
button press). Most users are used
to do that with devices such as TV sets, DVD players, even phones usually do
not
have a restart option.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.