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

List:       kde-panel-devel
Subject:    Re: PMC use case
From:       Christophe Olinger <olingerc () binarylooks ! com>
Date:       2010-03-30 12:43:17
Message-ID: 1718db771003300543o4fdd3e1boefdcb712566a82d2 () mail ! gmail ! com
[Download RAW message or body]

On Tue, Mar 30, 2010 at 2:25 PM, Marco Martin <notmart@gmail.com> wrote:
> On Tuesday 30 March 2010, Christophe Olinger wrote:
>> Hey everybody,
>>
>> I think it will be really difficult to have the UI scale from 50"
>> screens right down to 5" screens. At the moment we use a top panel for
>> playback control (and mode switching) and will use a bottom panel for
>
> i don't think the mode switching should ultimately be there, the modes should
> be shown as mammoth icons in a main menu in the browser itself, that would be
> a kind of "root folder" for it.
>
From the wiki:
On PMC startup the user will see a beautiful home applet that has (PMC
is meant to be fullscreen):

    * Buttons to switch to the following media modes: Pictures, Music,
Videos (later: Games, maybe an all Media Mode)
    * Area with information about your recently played media, highest
ratings, things that allow you to jumpstart to a specific media.
    * Possibility to add normal plasmoids, like note apps, web slice,...

So eventually only the home button will remain in the controller and
the home screen will be the root of everything. On media type switch
we will then alwys go via the home applet (2 clicks). At some point we
thought that having mode switch buttons in the controller would be
good to reduce switching to 1 click. At one point I imagined holding
the home button in the controller would make a sort of drawer expand
which would show the other mode buttons.

>> displaying information about media. The bottom panel might be reusable
>> for a big screen UI, but the playback control migth have to be
>> transformed into something else. Anyway, the way Alessandro designed
>
> as long as it scales big enough to be readable it will be perfectly fine.
> on a tv that thing will be purely informational since you won't click that
> buttons, because you would have play,stop, fast forward etc directly into the
> remote

anyway, the controller has a "toggle autohide" button, we can set it
to always autohide on big TV screens

>
>> the basic libs behind mediacenter should make it easy to have a second
>> UI widget for playback control that could replace the top panel in a
>> big screen scenario. I am not even sure that we have to do this. Maybe
>> the whole UI does scale up and down nicely. As soon as I get my patch
>> in, we can test this.
>
> yes it should, if there is some element that does it's wrong and it has simply
> to be discarded
>
>
>
>
> --
> Marco Martin
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]