user-skin mods for KiddaC skins

Dsayers custom mix plugin has now been skinned in all of my skins. So you do not need to install this skin_user_slyk-onyx.xml to skin this plugin from dsayers.

I will leave this thread open though, because it highlights the fact that you can mod any of my skins by adding in your modded screens to skin_user_(skin name).xml

Using that file any of your custom mods do not get overwritten when you update any of my skins.

If it wasn't for the modding crew when I was creating my skins, they wouldn't look like they do now. So feel free to have a play.

Your mods might even end up in my skins.

both are in my skins :)

Hi Dsayers,

What exactly do the custom mix and channel importer plugins do?

Cheers!

Cheers!

Don't use ABM, But thanks for clearing up.

Hi kiddac I was wondering if you could point me in right direction here. A friends wife has glaucoma and finds your onyx skin easiest on the eyes with the exception of one screen which is this one or it's alternative4c33aae5b54dd77c869691.jpg

I can alter text size of middle pane in settings. However the info on left pane and particularly the right side she struggles with and I cannot for the life of me find a way to make it larger. Is there anything I can do to alter text size on either pane. Wasn't sure if I should post here or in the main thread. apologies if in wrong place

This is the alternative channel selection screen you are showing.

On this alternative screen you can change the size of the fonts on the left, but the font on the right might be problematic as it is bringing in all them times via my custom OnyxNextEvents2 python component. (it might work).

The screen is

.\usr\share\enigma2\slyk-onyx\

o-channel-selection.xml

<screen name="SlimChannelSelection" ....

If you open up o-channel-selection.xml in an xml editor like xml wrench (free), you will see I have titled comments for each section. So you should easily be able to find the elements to edit. For example

<!-- now programme -->

<widget source="ServiceEvent" render="Label" position="20,21" size="281,20" font="Bold;18" foregroundColor="colour2" backgroundColor="#25000000" transparent="1">

<convert type="EventName">NowName</convert>

</widget>

<widget source="ServiceEvent" render="RunningText" options="movetype=running,startpoint=0,direction=top,steptime=80,repeat=0,always=0,oneshot=0,startdelay=6000,wrap"

position="20,48" size="281,173" font="Regular;16" foregroundColor="white" backgroundColor="#25000000" transparent="1">

<convert type="EventName">FullDescription</convert>

</widget>

The panel on the right is this section.

<widget source="ServiceEvent" render="OnyxNextEvents2" position="1000,220" size="240,500" font="Regular;14" start="0" lines="26" foregroundColor="white" backgroundColor="#25000000" noWrap="1" transparent="1">

<convert type="ServiceName">Reference</convert>

</widget>


If you change the right panel, I don't know whether or not you can change the number lines or not. I would change the font size first, then experiment with the number of lines to see if it causes any problems. I never wrote this component, its someones elses code I amended for my skin. So I don't know how it fully works and I cant remember if I hard coded in the number of lines, or whether that lines variable does anything or not.

If its just the standard channel select screen that is this screen

\usr\share\enigma2\slyk-onyx\

o-channel-selection.xml

<screen name="ChannelSelection" ....

<!-- next programme -->

<widget source="ServiceEvent" render="Label" position="1000,255" size="260,44" font="Bold;18" foregroundColor="colour2" backgroundColor="midright" transparent="1">

<convert type="EventName">NextName</convert>

</widget>

<widget source="ServiceEvent" render="Label" position="1000,296" size="260,22" font="Regular;18" foregroundColor="white" backgroundColor="midright" noWrap="1" transparent="1">

<convert type="EventTime">NextStartTime</convert>

<convert type="OnyxClockToText">SlykQStartTime</convert>

</widget>

<widget source="ServiceEvent" render="Label" position="1000,341" size="260,218" font="Regular;15" foregroundColor="white" backgroundColor="midright" transparent="1">

<convert type="EventName">NextDescription</convert>

</widget>

<!-- Next Events List -->

<panel name="h-separator-br" />

<widget source="ServiceEvent" render="OnyxNextEvents" position="1000,604" size="260,48" font="Regular;14" start="2" lines="3" foregroundColor="white" backgroundColor="botright" noWrap="1" transparent="1">

<convert type="ServiceName">Reference</convert>

</widget>

Many thanks Kiddac will have a play on my receiver and see if I can change successfully without breaking anything else and if ok will apply to her receiver at weekend. Will let you know result in case it helps anyone else, for the record you sir are a gent

Just an update managed to alter text size in both panels in the slim channel selection screen, the panel on right I was able to change the amount of lines with no problem either. Had to alter positions and size of service title boxes in left pane, and position and size of items in right pane to allow room for the larger text but it now looks ok . I sent the lady some pictures of screen and she is happy with end result. Thanks again Kiddac

When somebody points you to the right place and tells you what you need to do and while there you get to see what altering one thing affects it is an eye opener, working out how to alter something else to allow for your previous change was quite fun. How the hell you know how to do this from scratch and tie everything in to look so good is beyond me, Skinner will not be in my list of accomplishments, skin bodger may be though. I am not going to post a screenshot your ocd/faffiness will go into meltdown mode.

dsayers ... throw me a friggen bone here. What are your new screen names.

old ones were

<screen name="DsayersCustomMixImporterScreen"

<screen name="ChannelsImporterScreen"

1999gtv ... how do you think any skinner starts... They start with faffing. Moving this... resizing that... new graphic for this... etc. Next minute... 2 years of your life has gone by in a blink. ha. We used to have a good community of everyone having a go with skin modding, unfortunately there is very little of it about nowadays. As I always say, I just give you a full base to work on. It's up to the user if then can be arsed to make the skin their own.

I will assist anyone willing to get there hands dirty and have a go. I have no time for people that want you to make all the amends for them though, despite me giving clear instructions on how to do it.
If you bootloop your box... so what... undo your amends ... faff again... learn form your mistakes ... faff some more... have some gratification that you have achieved something. :thumbup:

Dsayers.. dropbox skins updated to reflect the new name of your plugin.

Jensen... exactly, the hours skinners put in to make these skins only a skinner will know. Unsung heroes. Its an endless cycle of write code, test code, crash box, tweak code, test code, crash box. Not even adding to the equation the hundreds of hours of research I put in in the early days when I didn't have a clue what I was doing. I also don't use openskin designer due to the template nature of my skins, so pretty much every single screen I mockup in photoshop first, code it, and then overlay the output onto my photoshop mockup to then fine tweak it.

Writing a skin can be reasonably straightforward once you know the basics. I could probably mockup a skin in a week, write all the code in 4 weeks, but then take another 8 weeks to perfect it, then another year until it is finally totally bug free. Its fine tuning and bug fixing that is time consuming. Although I am pretty much retired now due to being warn out from all the hard work, I still recommend people have a go. You also learn so much about enigma2 sateliite boxes in the process. Knowledge I would have never gained if I wasn't delving into all the python components on a daily basis to work out what I can and cannot put into a skin.

I have the benefit of being a graphic designer for 20 years, so the graphic side is no problem, but I am also a programmer so it was a perfect hobby for me to do. But even without perfect graphic skills, or a technical know how, there is a wealth of information scattered all over the internet. Start little... in the end you will make a skin. (and remember if you borrow some one elses code or graphics, have the decency to mention or credit them :) )

If you know my history... my first project was.. oh lets just tidy up the original blue hd skin... and look where that ended up. Before that, I had absolutely no knowledge of enigma2 or skinning at all on these boxes.

Enigma2 isn't the easiest platform to work with, in fact its probably the worst I have ever encountered, but there is now hope things are moving more slowly to android based, then I might come back out of retirement. Because working with android will be like heaven compared to this old creeking code. It was still fun though. Stressful, but very worth while.