PMC use case

Christophe Olinger olingerc at binarylooks.com
Tue Mar 30 15:53:12 CEST 2010


On Tue, Mar 30, 2010 at 3:46 PM, Marco Martin <notmart at gmail.com> wrote:
> On Tuesday 30 March 2010, Christophe Olinger wrote:
>> On Tue, Mar 30, 2010 at 3:15 PM, Marco Martin <notmart at gmail.com> wrote:
>> > On Tuesday 30 March 2010, Christophe Olinger wrote:
>> >> On Tue, Mar 30, 2010 at 2:25 PM, Marco Martin <notmart at 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,...
>> >
>> > do you plan to make that home applet the top bar?
>>
>> No, the home applet should be the first thing that the user sees. Upon
>> entering a mode, the top and bottom bars appear
>>
>>
>> is not fullscreen enough,
>>
>> > and put all the possible mode here will quickly run out of space an be
>> > cluttered, in the bar there should be a single button, triggered also
>> > from a single real key (could be esc or home, or whatever in keyboards,
>> > the more adapt case by case on remotes)
>> > that "home applet" if you want it really isolated could be a different
>> > containment, so would be a totally standaloe fullscreen thing, but i
>> > don't think i like it.
>>
>> I more thought of it as an additional applet. On switching to home
>> mode, everything hides and the home applet appears
>>
>> > i really do think it should be right into the browser, the "modes"
>> > together eventual plugins to do other stuff should be right into the
>> > browser as items, so they can be as big as possible taking the whole
>> > screen or scale decently if some day there will be many of them.
>>
>> the general PMC home applet does not have a browser. each mode has its
>> own specific home applet which actually is a browser which shows media
>> specific dataengines. This one will have big icons
>
> i fear this is just useless code duplication, really.
> for this fullscreen menu you need exactly the same functionality of the
> browser.


Wouldn't it just be different startup models?


(see ugly mockup here: general home applet at the bottom)

http://imagebin.ca/view/uEvKL2.html



>
> Cheers,
> Marco Martin
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>


More information about the Plasma-devel mailing list