Tweaking the Blue

[zehd]

I'm trying to tweak the Blue skin, and I'm lost. Sorta lost...

I'm trying to enlarge the fonts for a few places. Ideally I'd like to be able to see something and know what to tweak. So far, I'm just guessing. I was hoping there'd be a convention...

Anyway, in TVGuide/skin.xml I can adjust the time line and listing style.
[ATTACHMENT NOT FOUND]

But if I select a specific episode, I can't find where the text style is stored...
[ATTACHMENT NOT FOUND]

I also want to change others lists like Recording and Video panels, and their detail screens.

I KNOW this has been covered before, I just haven't seen a really easy way to interpret the screens fields...

[Fatman_do]

Are you looking at the Popups directory? There are various popups there for the TVGuide.

[zehd]

Are you looking at the Popups directory? There are various popups there for the TVGuide.

Thanks. You know I'm starting to find stuff especially a TextStyle defined in the Baseskin.xml that is used elsewhere.

However if I understand it I can create my own text styles (leave the other ones behind for compatibility) and then modify the elements to use my new textstyles...

Now here's the rub, I can't find docs on supported textstyle values, I don't know the syntax for placement or location, and I'm unable to easily see what component (pic, button, text box) is used to create a page) The Advisor doc seems out of date, Is it, or maybe I am...

After tweaking one skin for the MVP I'm going to try making the LCars skin for Community but I don't know how to start writing for it.

It does seem like a club that is not easily joined, with out knowing the secret handshake...

[Fatman_do]

I started a CommunitySkin tutorial thread but I put it on hold during the beta phase of the latest version of gbpvr due to new menu elements.

http://forums.nextpvr.com/showthread.php?t=33070

This may give you some exposure to textstyles.

In general, if a textstyle called for in a particular skin.xml file is not defined in that file, GB-PVR will then look in the Baseskin.xml file for that textstyle.

A simple fix then is, if you want a different size in that screen or popup only, just copy that textstyle line from the baseskin.xml file to the skin file you are editing. From there, make adjustments in size, color or font.

You can use any name for a textstyle, you just have to define it and then later, call for it.

You may find it easier to do the tip I suggested and not bother with different names.

BTW, there is no club or secret handshake with the CommunitySkin. Everybody is a equal partner. There are some tricks to it that are actually intended to make it easier to tweak, but I have to do a better job of explaining it (hence the tutorial).

Bang on me for answers as much as you like, I am here to help.

[zehd]

I started a CommunitySkin tutorial thread but I put it on hold during the beta phase of the latest version of gbpvr due to new menu elements.

http://forums.nextpvr.com/showthread.php?t=33070

This may give you some exposure to textstyles.

In general, if a textstyle called for in a particular skin.xml file is not defined in that file, GB-PVR will then look in the Baseskin.xml file for that textstyle.

A simple fix then is, if you want a different size in that screen or popup only, just copy that textstyle line from the baseskin.xml file to the skin file you are editing. From there, make adjustments in size, color or font.

You can use any name for a textstyle, you just have to define it and then later, call for it.

You may find it easier to do the tip I suggested and not bother with different names.

BTW, there is no club or secret handshake with the CommunitySkin. Everybody is a equal partner. There are some tricks to it that are actually intended to make it easier to tweak, but I have to do a better job of explaining it (hence the tutorial).

Bang on me for answers as much as you like, I am here to help.

All righty then... I'll finish an idea here and then keep it going in the thread...

I se things going the exact other direction. All text styles for all components dfined in the Baseskin.xml and none in the skin files themselves..

Sure, if you want a header to be italic in one very specific spot on one skin, you could add the extra tag...

Anyway, I'm playing with writing a program that searches and replaces within the entire skin directory structure. I'm writing the routine that will yank all textstyle name= tags out of skins and place them in the TextStyles section of the baseskin.

Then once all the TextStyles are defined in one place, a person can edit just the one xml and have the changes reflect in all skins at the same time, adding a consistent uniform look.

Once I get this working right, I'll be looking to see if I'm on the right track as far as the community is, and offer it.

I'll be looking into playing with placement and locations too, and maybe even create a WYSIWYG skin editor...

Your thoughts?

[Fatman_do]

All righty then... I'll finish an idea here and then keep it going in the thread...

I se things going the exact other direction. All text styles for all components dfined in the Baseskin.xml and none in the skin files themselves..

Sure, if you want a header to be italic in one very specific spot on one skin, you could add the extra tag...

Anyway, I'm playing with writing a program that searches and replaces within the entire skin directory structure. I'm writing the routine that will yank all textstyle name= tags out of skins and place them in the TextStyles section of the baseskin.

Then once all the TextStyles are defined in one place, a person can edit just the one xml and have the changes reflect in all skins at the same time, adding a consistent uniform look.

That is pretty much what I did with the CommunitySkin. Most general textstyles are there. The ones that were really of any value to a specific plugin (say certain ones in Weather) I left there. That is how the CommunitySkin applies themes. A different baseskin.xml file will define different fonts, colors, and such. Then, all screens will have a new look.

Once I get this working right, I'll be looking to see if I'm on the right track as far as the community is, and offer it.

I'll be looking into playing with placement and locations too, and maybe even create a WYSIWYG skin editor...

Your thoughts?

Sounds like a good idea. I know a WYSIWYG skin editor would be outstanding. There was a Skin Editor on the wiki called SkinEdit, but it is incompatible with PVRX2. It is hosted on a SourceForge page, so maybe it may have something to offer you.

If you have any other questions or suggestions, fire away.

[zehd]

That is pretty much what I did with the CommunitySkin. Most general textstyles are there. The ones that were really of any value to a specific plugin (say certain ones in Weather) I left there. That is how the CommunitySkin applies themes. A different baseskin.xml file will define different fonts, colors, and such. Then, all screens will have a new look.



Sounds like a good idea. I know a WYSIWYG skin editor would be outstanding. There was a Skin Editor on the wiki called SkinEdit, but it is incompatible with PVRX2. It is hosted on a SourceForge page, so maybe it may have something to offer you.

If you have any other questions or suggestions, fire away.

I've been trying to tweak the blue, but I bet it's better to look at a community skin... thanks