Community Skin-WS 1.0 released.

[Fatman_do]

Theater Listings doesn't scale to HD resoluiton (hardcoded to 720x480). I can include it the best I can, but I think some functions of the plugin are currently broken due to fandango changing its website.

InternaltionalCinemaListings has added support for Zap2it for USA/Canada, and it is skinned for Community-WS already (I just need to make a slight change). I'll add WebCams also.

[topster]

Theater Listings doesn't scale to HD resoluiton (hardcoded to 720x480). I can include it the best I can, but I think some functions of the plugin are currently broken due to fandango changing its website.

InternaltionalCinemaListings has added support for Zap2it for USA/Canada, and it is skinned for Community-WS already (I just need to make a slight change).

Ah, didn't know that. Well, since the international version works in the US, that's good enough for me.

I'll add WebCams also.

Thanks a bunch! And if there are no other requests for plugin skinning, maybe you can also do Sports Scores.

Thanks for the effort, Fatman! All these visual enhancements really help make GBPVR!

[Fatman_do]

2007–Mar–04 : Version 1.0.7 released.
*Updated for GB-PVR 99.12.
*SearchWiz added and Task image support for plugin. (not added yet)
*Added WebCams2.
*Added ScreenSaverPlugin.
*Fixed an issue with TV Guide related to GB-PVR 99.12 release.

Topster, will get working on SportScores, but it may take me some time. I don't have as much time as I had in the past with my new job working 55hrs. a week....

[topster]

Topster, will get working on SportScores, but it may take me some time. I don't have as much time as I had in the past with my new job working 55hrs. a week....

Hi Fatman, no worries! I'm just glad that you're doing this at all. Thanks for supporting the webcam plugin! I'll give it a spin.

[topster]

Hi Fatman,

I played around with your skin and it looks great. I have a couple of questions though.

In the OSD guide, I'm seeing this:


Notice that it's much bigger than the actual screen? I recall reading that this needs to be fixed by Sub and there's nothing you can do from the skin side. Is that right?

Also, when I go into Live TV by choosing a show from TV Guide, show the OSD guide, exit the OSD guide, and exit Live TV back into TV Guide, my TV Guide gets messed up and I see this:


Is this a skin issue? If I just go to TV Guide from the main menu, it looks fine (except for the channel logos -- see below).

Finally, what do I need to modify in the skin file to change the format of the channel logos in TV Guide back to the one supported in Community 4:3 skin? It looks a little compressed in the 16:9 skin.


Thanks for the great work!

[Fatman_do]

Hi Fatman,

I played around with your skin and it looks great. I have a couple of questions though.

In the OSD guide, I'm seeing this:


Notice that it's much bigger than the actual screen? I recall reading that this needs to be fixed by Sub and there's nothing you can do from the skin side. Is that right?

I'll look into that, it may be something I can fix.

Also, when I go into Live TV by choosing a show from TV Guide, show the OSD guide, exit the OSD guide, and exit Live TV back into TV Guide, my TV Guide gets messed up and I see this:


Is this a skin issue? If I just go to TV Guide from the main menu, it looks fine (except for the channel logos -- see below).

That is a bug that sub is aware of I think. Seems like Ted the Penguin pointed that out.

Finally, what do I need to modify in the skin file to change the format of the channel logos in TV Guide back to the one supported in Community 4:3 skin? It looks a little compressed in the 16:9 skin.


Thanks for the great work!

Unfortunately there is nothing that can be done to widen that column. Its width is hard coded.

Thanks for pointing these things out.

[Ted the Penguin]

That is a bug that sub is aware of I think. Seems like Ted the Penguin pointed that out.

yeah, sub fixed it, there is a thread in the support forum with a fix for it, but it will be included in the next release as well.

Unfortunately there is nothing that can be done to widen that column. Its width is hard coded.

that is mostly true, you can fix the ratio of the icons by changing the height of the channel rows. I think a height of 46 made them look pretty good (using the ones from lyngsat logo)

another option is to figure out the exact size of the icons when they are displayed, and stretch your logos so they are the correct ratio when stretched to that size... could get tedious.

[Ted the Penguin]

hey, I figured you would find this interesting.

in an effort to make things cleaner and more Object oriented in my skins, I have started using DrawCompositeImage for lots of things, like this

Code:

<CompositeImage name="DetailsViewNormalFolder" size="680,60">
    <DrawImage filename="..\_res\list_sep.png" size="664,3" loc="8,54"/>
    <DrawText text="@categoryName" loc="10,0" size="660,45" textStyle="Folders" align="Left"/>
</CompositeImage>

<CompositeImage name="DetailsViewSelectedFolder" size="680,60">
    <DrawImage filename="..\_res\list_middle.png" size="680,50" loc="0,0"/>
    <DrawCompositeImage name="DetailsViewNormalFolder" loc="0,0" size="680,60"/>
</CompositeImage>

and basically most everywhere that code is replicated. makes it easier to tweak lists, also it ensures that the normal and selected image look the exact same.

you can also do things like this,

Code:

<CompositeImage name="AlbumInfoScreenTrack" size="680,40">
    <DrawText text="@TracknumberPlusDot" loc="5,3" size="50,30" textStyle="TrackNumber" align="Left"/>
    <DrawText text="@Name" loc="40,3" size="450,30" textStyle="@TrackType" align="Left"/>
    <DrawText text="@Duration" loc="500,3" size="130,24" textStyle="TrackDuration" align="Right"/>
</CompositeImage>
<CompositeImage name="AlbumInfoScreenTrack-Normal" size="680,40">
    <DrawCompositeImage name="AlbumInfoScreenTrack" loc="0,0" size="680,40" parameters="@TrackType=TrackNormal"/>
</CompositeImage>
<CompositeImage name="AlbumInfoScreenTrack-Normal-Marked" size="680,40">
    <DrawCompositeImage name="AlbumInfoScreenTrack" loc="0,0" size="680,40" parameters="@TrackType=TrackMarked"/>

since I noticed in the community skin you use different text styles.


do you know how efficient is to use this, how much overhead does this create, the nested image draws

just thought you could use it to make the community skin a bit cleaner (and by cleaner I mean the skin files themselves being cleaner)

[Fatman_do]

hey, I figured you would find this interesting.

in an effort to make things cleaner and more Object oriented in my skins, I have started using DrawCompositeImage for lots of things, like this

Code:

<CompositeImage name="DetailsViewNormalFolder" size="680,60">
    <DrawImage filename="..\_res\list_sep.png" size="664,3" loc="8,54"/>
    <DrawText text="@categoryName" loc="10,0" size="660,45" textStyle="Folders" align="Left"/>
</CompositeImage>

<CompositeImage name="DetailsViewSelectedFolder" size="680,60">
    <DrawImage filename="..\_res\list_middle.png" size="680,50" loc="0,0"/>
    <DrawCompositeImage name="DetailsViewNormalFolder" loc="0,0" size="680,60"/>
</CompositeImage>

and basically most everywhere that code is replicated. makes it easier to tweak lists, also it ensures that the normal and selected image look the exact same.

you can also do things like this,

Code:

<CompositeImage name="AlbumInfoScreenTrack" size="680,40">
    <DrawText text="@TracknumberPlusDot" loc="5,3" size="50,30" textStyle="TrackNumber" align="Left"/>
    <DrawText text="@Name" loc="40,3" size="450,30" textStyle="@TrackType" align="Left"/>
    <DrawText text="@Duration" loc="500,3" size="130,24" textStyle="TrackDuration" align="Right"/>
</CompositeImage>
<CompositeImage name="AlbumInfoScreenTrack-Normal" size="680,40">
    <DrawCompositeImage name="AlbumInfoScreenTrack" loc="0,0" size="680,40" parameters="@TrackType=TrackNormal"/>
</CompositeImage>
<CompositeImage name="AlbumInfoScreenTrack-Normal-Marked" size="680,40">
    <DrawCompositeImage name="AlbumInfoScreenTrack" loc="0,0" size="680,40" parameters="@TrackType=TrackMarked"/>

since I noticed in the community skin you use different text styles.


do you know how efficient is to use this, how much overhead does this create, the nested image draws

just thought you could use it to make the community skin a bit cleaner (and by cleaner I mean the skin files themselves being cleaner)

As you might have seen I due something like that, but just haven't taken it that far....yet.

The Community Skin 2.0 release was the proof of that method. Long term, 3.0 is going to do those things to minimize code and image names in every plugin where possible.

I haven't tested fully, but I think the overhead impact is not significant as far as I can tell.

[Ted the Penguin]

sub said that the overhead should be negligible, I have done this in many parts of the sassari_red skin, however you CANT draw elements using that method, so the OSD cant be done like this (no matter how much I might want it to be)