Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 10 of 10

Thread: How to use user_skin_mod.xml with common skins?

  1. #1
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,752
    Thanks
    472
    Thanked 606 Times in 432 Posts

    How to use user_skin_mod.xml with common skins?

    Hi I've been experimenting with YouViX skin mods, the modifications I need to do are in the skin_YouViX.xml these modifications override on software updates.

    How could we use user_skin_mod.xml? I've tried naming the file to skin_user_YouViX-Common.xml but this doesn't seem to work.
    Last edited by dsayers; 07-03-19 at 18:10.

  2. #2
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,752
    Thanks
    472
    Thanked 606 Times in 432 Posts
    Sorry just tried again, what I need to do is use the name of the skin ie skin_user_YouViX-Blue.xml although it would be good if we could use a user skin mod for common folder then we wouldn't need multiple mod files for each YouViX skins.

  3. #3
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by dsayers View Post
    Sorry just tried again, what I need to do is use the name of the skin ie skin_user_YouViX-Blue.xml although it would be good if we could use a user skin mod for common folder then we wouldn't need multiple mod files for each YouViX skins.
    The whole point about the naming is that it allows you to have multiple overrides present at the same time, one for each skin you are using.
    If you want to have a skin_user_YouViX-Common.xml (presumably just to contain overrides for YouViX-Common code), then just end your skin_user_YouViX-Blue.xml (and skin_user_YouViX-Pink.....xml) with:
    Code:
    <!-- ALL includes must be in this file!
         The include code doesn't handle includes in includes.
     -->
    <include filename="/etc/enigma2/skin_user_YouViX-Common.xml">
            
    </skin>
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  4. The Following 2 Users Say Thank You to birdman For This Useful Post:

    dsayers (08-03-19),Willo3092 (08-03-19)

  5. #4
    clivejo
    Is there a guide or documentation on how Skins work? I have some override settings for the VIX Dark skin that I want to keep (after a package update for example)

    Also what do you guys use for skin design? I came across this project which I built from source - https://gitlab.com/technic93/e2designer but I can't seem to be able to use it to modify ViX Dark skins due to the nestled nature of the skins.

  6. #5
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by clivejo View Post
    Is there a guide or documentation on how Skins work?
    Not that I've found.
    I have some override settings for the VIX Dark skin that I want to keep (after a package update for example)
    See the previous post to yours. You need to put a skin_user_<<skin_name>>.xml file into /etc/enigma2 with the changes you want. This gets preserved over updates (an is in backups).
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  7. #6
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,752
    Thanks
    472
    Thanked 606 Times in 432 Posts
    Quote Originally Posted by clivejo View Post
    Also what do you guys use for skin design? I came across this project which I built from source - https://gitlab.com/technic93/e2designer but I can't seem to be able to use it to modify ViX Dark skins due to the nestled nature of the skins.
    That looks similar to open skin designer and works great for certain skins, sadly it doesn't work with most skins.

    For me it's guess work but looking at positions etc of other parts of the skin and do one step at a time. Some skins I'm used to now and it will probably be the same for you once you start editing you'll get an idea of how screens are done on your favourite skin.

  8. #7
    clivejo
    Quote Originally Posted by dsayers View Post
    Some skins I'm used to now and it will probably be the same for you once you start editing you'll get an idea of how screens are done on your favourite skin.
    What is your favourite skin?

  9. #8
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,752
    Thanks
    472
    Thanked 606 Times in 432 Posts
    Quote Originally Posted by clivejo View Post
    What is your favourite skin?
    It's hard to say what a favourite skin is as I know how much work skinners put in there skins. Preference is v-skin1080, slyk onyx 1080. Simple ten eighty is a nice skin to play around with aswel.

    Only way to find out what is best for you is installing one see what it's like and try another.
    Last edited by dsayers; 02-06-19 at 00:39.

  10. #9

    Title
    Forum Supporter
    Donated Member
    Join Date
    Aug 2019
    Posts
    26
    Thanks
    1
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by birdman View Post
    See the previous post to yours. You need to put a skin_user_<<skin_name>>.xml file into /etc/enigma2 with the changes you want. This gets preserved over updates (an is in backups).
    I can't get this to work and I keep losing my changes on update. Do you have an example of how the files should be named and the content of the files? ie on github or gitlab etc?

  11. #10
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by clivejo View Post
    I can't get this to work and I keep losing my changes on update. Do you have an example of how the files should be named and the content of the files? ie on github or gitlab etc?
    This is what I have, and where:

    Code:
    root@et8000:/etc/enigma2# ls *skin*
    gml-test-skin.xml                     skin_user_ViXBMC_1080_Confluence.xml
    skin_extra.xml
    and here are the files. Read the comments (and spot the incorrect one...).

    skin-files.zip
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  12. The Following User Says Thank You to birdman For This Useful Post:

    deejayh (30-03-20)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.