Apollo One (4 Viewers)

[morpheus_xx]

@offbyone yep, agree.

Only the "ViewModeModel" should be extended to offer only supported (inbuilt) views. I thought about this before but haven't implemented anything.

Also I like to repeat: a 3D coverflow would not match the design, I agree. But a nice 2D version does fit. I think @wizard123 can create some nice ideas here as well

Anyway, I like the discussions

 

[wizard123]

Also I like to repeat: a 3D coverflow would not match the design, I agree. But a nice 2D version does fit. I think @wizard123 can create some nice ideas here as well

Yes i agree a 2D cover flow COULD fit provided it's designed to fit not just added randomly from another skin if you know what i mean

 

[Lehmden]

If you implemented a view into a design and it did not fit/ looked terrible

Same happens with plugins that are not directly supported by the skin and use default skin files as fallback. In fact it is working, but looking terrible for most plugins without adapted skin files (means for nearly all plugins that are installed separately).
Once again, I don't need CoverFlow myself but it simply has to be there imho. If it is a 2D CoverFlow, I'm fine with... It's like the breadcrumb menu on top (or bottom on some skins). Personally I really don't like this, but it's part of every skin since the beginning...

I have a completely different question. Sorry for being off topic but here are the people who probably can answer this...
Is there a way to create a skin completely without a "home" screen in MP2 recently? I was thinking about a "flying" menu above the recent screen if you press the "green button" (or the equivalent for mouse or touch). On MP2 start the last used screen/plugin should be displayed. So no use for a home screen at all. Just a rough idea but maybe something that can look and work nicely. A bit like the opposite to Apollo One where it looks as if you never leave the "home" screen at all.

 

[offbyone]

I have brought up a skin idea like that before. (Don't want to find the thread - somewhere with the spiderweb panel). The home screen should not be a menu, but more an information of latest media, news, current+coming weather, .. stuff like that. And there should be a "menu" button on the remote that brings up the root menu as overlay from any screen. It would be possible with MP2.
(please someone move these posts out of here if there are going to be more)

 

[wizard123]

Once again, I don't need CoverFlow myself but it simply has to be there imho.

I don't think your getting it, no specific view HAS to be there in mp2. The views that are there are the views created for the skin which could be completely different like a stack of books on a shelf and the selected item has focus showing the cover for example. Just because coverflow has always been a view in mp1 does not mean it has to be there in mp2 or in any particular skin.

 

[kilik360]

Just because coverflow has always been a view in mp1 does not mean it has to be there in mp2 or in any particular skin.

I agree with this view, I think that skinner should do what their imagination tells them. I think we can tell a skin "complete" if the skinner himself tell it is. Other views, for example, don't "have to be" in skin, it's the skinner choices. Of course he can takes requests. But I don't think it's good to say "you have to do this".

Like I said it's up to the skinner what he integrates or not.

thanks wizard123 and morpheus_xx! It's good to see you work together!

 

[ge2301]

@morpheus_xx
I checked the blue focus box for list view media items and it looks not so bad. Good work
With opacity of 0.7 instead of 1 it could look better, because the blue will fit better to the background and the box is less offensive.
I could not find out, how you set the gradient color in the background. Changing the opacity in ButtonControlStyle also unfocused buttons are affected. Changing the trigger for focused buttons from
<Setter TargetName="ButtonControlRectangle" Property="IsVisible" Value="True"/>
to
<Setter TargetName="ButtonControlRectangle" Property="Opacity" Value="0.7"/>
does not work.

 

[morpheus_xx]

The Opacity of the button background is animated by a so called StoryBoard (started by triggers in button definition):
https://github.com/MediaPortal/Medi...ne/themes/default/styles/Buttons.xaml#L16-L21

Here you find the end opacity of "1", this you can adjust.

I have chosen the "blue" color because I didn't know the opacity value that was used in the mockup (well I might have calculated the factor, but I went the easier route and took RGB from image).

 

[ge2301]

The Opacity of the button background is animated by a so called StoryBoard (started by triggers in button definition):
https://github.com/MediaPortal/Medi...ne/themes/default/styles/Buttons.xaml#L16-L21
Here you find the end opacity of "1", this you can adjust.
I have chosen the "blue" color because I didn't know the opacity value that was used in the mockup (well I might have calculated the factor, but I went the easier route and took RGB from image).

I have changed it from 1 to 0.6 and removed the frame. Like this it fits much better to the color setting and style of the skin.


Edit: I'll check also 0.7 and 0.8 opacity values later and compare the result. 0.6 was only based on first feeling.

 

[ge2301]

@wizard123
Can you prepare a mock-up for the Cover-flow view? I think we are align, that it should be 2D to fit to the the overall skin.
Since the covers will be large, there could be a small overlay symbol in the upper right corner to mark un-/watched videos. I understood the red tabs for the list view were used in order not to cover 30% of the cover Anyway a mock-up would be helpful to see where to go.