- Moderator
- #1
Hi all
One of the big "behind the scenes" changes I made between BleazleWide V6 & V7 was the reduction in the number of fonts used. This has resulted in a far smaller fonts cache but also means that if you use an xml file from Blue3Wide to run a plugin if a font is called that isn't used in BleazleWide you'll end up with the default MP font which is a bit small Apart from that the fact that the skin is based on B3W means that any plugins supported in B3W are also supported by BleazleWide.
I'm not going to try and support every plugin out there "officially" (with sliding graphics and font changes etc) so here's what you can do if you have a plugin that you want to use that requires a bit of tweaking:
1. Copy any XML & graphics files required by the plugin from the Blue3Wide directory to the appropriate BleazleWide directories
2. Run MP and check the plugin out - if you're happy with how it looks you're done
3. If some of the fonts look too small open the appropriate xml file(s) and look for the <font> tags
Here's a list of the fonts used in BleazleWide and a note of where I generally use which font followed by the name of the fonts in Blue3Wide which they replace:
font101 - height = 13 (Button labels etc, this is the main font used in the skin) - Replaces fonts 10, & 11
font14 - height =20 (Taglines/bigger text - headings etc. Also the size of typed search text for virtual keyboard) - Replaces fonts 15 & 16
font18 - height = 15 (Programme descriptions(plots). Also the size of text on virtual keyboard)-Replaces fonts 12, & 13
font103 - height = 30 (only used for the "now playing" preview window to show the time elapsed) - Replaces fonts BasicHome, 32, 48 & 60
The numbering is all over the place which is a result of a couple of things that were picked up during testing but it doesn't make any difference, you just have to make sure you replace fonts as indicated.
Once you've got it looking good feel free to add a post to this thread with the altered XML(s) file so that other BleazleWide skin users can use it too - it's a community thing after all so here's a chance to do your bit!
Bleazle.
One of the big "behind the scenes" changes I made between BleazleWide V6 & V7 was the reduction in the number of fonts used. This has resulted in a far smaller fonts cache but also means that if you use an xml file from Blue3Wide to run a plugin if a font is called that isn't used in BleazleWide you'll end up with the default MP font which is a bit small Apart from that the fact that the skin is based on B3W means that any plugins supported in B3W are also supported by BleazleWide.
I'm not going to try and support every plugin out there "officially" (with sliding graphics and font changes etc) so here's what you can do if you have a plugin that you want to use that requires a bit of tweaking:
1. Copy any XML & graphics files required by the plugin from the Blue3Wide directory to the appropriate BleazleWide directories
2. Run MP and check the plugin out - if you're happy with how it looks you're done
3. If some of the fonts look too small open the appropriate xml file(s) and look for the <font> tags
Here's a list of the fonts used in BleazleWide and a note of where I generally use which font followed by the name of the fonts in Blue3Wide which they replace:
font101 - height = 13 (Button labels etc, this is the main font used in the skin) - Replaces fonts 10, & 11
font14 - height =20 (Taglines/bigger text - headings etc. Also the size of typed search text for virtual keyboard) - Replaces fonts 15 & 16
font18 - height = 15 (Programme descriptions(plots). Also the size of text on virtual keyboard)-Replaces fonts 12, & 13
font103 - height = 30 (only used for the "now playing" preview window to show the time elapsed) - Replaces fonts BasicHome, 32, 48 & 60
The numbering is all over the place which is a result of a couple of things that were picked up during testing but it doesn't make any difference, you just have to make sure you replace fonts as indicated.
Once you've got it looking good feel free to add a post to this thread with the altered XML(s) file so that other BleazleWide skin users can use it too - it's a community thing after all so here's a chance to do your bit!
Bleazle.