<br><br><div class="gmail_quote">2010/3/30 Marco Martin <span dir="ltr"><<a href="mailto:notmart@gmail.com">notmart@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tuesday 30 March 2010, Christophe Olinger wrote:<br>
> On Tue, Mar 30, 2010 at 2:25 PM, Marco Martin <<a href="mailto:notmart@gmail.com">notmart@gmail.com</a>> wrote:<br>
> > On Tuesday 30 March 2010, Christophe Olinger wrote:<br>
> >> Hey everybody,<br>
> >><br>
> >> I think it will be really difficult to have the UI scale from 50"<br>
> >> screens right down to 5" screens. At the moment we use a top panel for<br>
> >> playback control (and mode switching) and will use a bottom panel for<br>
> ><br>
> > i don't think the mode switching should ultimately be there, the modes<br>
> > should be shown as mammoth icons in a main menu in the browser itself,<br>
> > that would be a kind of "root folder" for it.<br>
><br>
> From the wiki:<br>
> On PMC startup the user will see a beautiful home applet that has (PMC<br>
> is meant to be fullscreen):<br>
><br>
> * Buttons to switch to the following media modes: Pictures, Music,<br>
> Videos (later: Games, maybe an all Media Mode)<br>
> * Area with information about your recently played media, highest<br>
> ratings, things that allow you to jumpstart to a specific media.<br>
> * Possibility to add normal plasmoids, like note apps, web slice,...<br>
<br>
</div>do you plan to make that home applet the top bar? is not fullscreen enough,<br>
and put all the possible mode here will quickly run out of space an be<br>
cluttered, in the bar there should be a single button, triggered also from a<br>
single real key (could be esc or home, or whatever in keyboards, the more<br>
adapt case by case on remotes)<br>
that "home applet" if you want it really isolated could be a different<br>
containment, so would be a totally standaloe fullscreen thing, but i don't<br>
think i like it.<br>
<br></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
i really do think it should be right into the browser, the "modes" together<br>
eventual plugins to do other stuff should be right into the browser as items,<br>
so they can be as big as possible taking the whole screen or scale decently if<br>
some day there will be many of them.<br></blockquote><div><br></div><div>This is how the browser currently works. It starts showing available plugins to use for browsing. And i do agree with this behavior. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
the "adding normal plasmoids" part divides in two categories:<br>
tiny plasmoids with a brief informational value:<br>
couldbe put somewhere in the main containment, an rssnow with finally some<br>
adaptments for panels could be put in the bottom bar for instance, or we could<br>
want an analog clock somewhere in the screen while a videos is playing and the<br>
controls/info are shown on top, just because we can...<br>
<br>
or on the other hand there could be some plasmoid that scale well as full<br>
screen things, like a browser or a way more detailed version of the weather<br>
applet, those could take their own containment and be shown as fullscreen,<br>
launched from the browser<br>
<div class="im"><br>
> So eventually only the home button will remain in the controller and<br>
> the home screen will be the root of everything. On media type switch<br>
> we will then alwys go via the home applet (2 clicks). At some point we<br>
> thought that having mode switch buttons in the controller would be<br>
> good to reduce switching to 1 click. At one point I imagined holding<br>
> the home button in the controller would make a sort of drawer expand<br>
> which would show the other mode buttons.<br>
><br>
> >> displaying information about media. The bottom panel might be reusable<br>
> >> for a big screen UI, but the playback control migth have to be<br>
> >> transformed into something else. Anyway, the way Alessandro designed<br>
> ><br>
> > as long as it scales big enough to be readable it will be perfectly fine.<br>
> > on a tv that thing will be purely informational since you won't click<br>
> > that buttons, because you would have play,stop, fast forward etc<br>
> > directly into the remote<br>
><br>
> anyway, the controller has a "toggle autohide" button, we can set it<br>
> to always autohide on big TV screens<br>
><br>
<br>
</div>it should -always- be autohide and what is lacking at the moment is a way to<br>
decide what autohide at the proper moment.<br>
when you are watching a movie you can want to unhide only the top bar ith the<br>
progress and the bottom bar with informations.<br>
<br>
another thing is when you decide you want something else, so you could want to<br>
unhide the browser and/or the playlist. the two things don't make much sense<br>
shown at the same time, really.<br>
<br>
Cheers,<br>
<div><div></div><div class="h5">Marco Martin<br>
_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Alessandro Diaferia<br>KDE Developer<br>KDE e.V. member<br><br>