Nuke Evolution Generic

  • Moin,


    Ich habe mal auf die Schnelle meinen Skin Nuke.Evo so abgespeckt, das er mit DMM Images nutzbar ist. Konkreter Anlaß ist, das ich auf der One ein mir genehmes Aussehen brauche ... :P


    • läuft auf generischen DMM Images ab OE2.5 (also auch auf dem OE2.6 der One)
    • keine externen Skincomponents/Renderer/Converter
    • umfassende Pluginuterstützung
    • Full HD (1920x1080)



    Mein Schwerpunkt wird in Zukunft nun nicht gerade in der Weiterentwicklung dieser Skinvariante zu sehen sein, aber ich möchte euch das Ergebnis nicht vorenthalten.

  • dreamer-flt

    Changed the title of the thread from “NUke Evolution Generic” to “Nuke Evolution Generic”.
  • Moin,


    Nuke.Evo updated to V1.1.0


    • changed default color style to "Evolution" (same as in the original merlin skin)


    • added color designs, switchable with MerlinSkinThemes (available on the feed)



    11 designs are available:


    • Evolution
    • Evolution (no borders)
    • Evolution (white borders)
    • Evolution transparent
    • Neutrino (the blue thing visible in th first post of this thread :D)
    • Neutrino (no borders)
    • Neutrino transparent
    • Technisat b&w
    • Evolution bicolor
    • Black
    • Black (whte borders)


    Das muss jetzt aber reichen. Ich bin nicht so beschränkt wie viele denken um nicht zu sehen, das der Skin doch eher auf bestehenden Systemen mit ominösen Images zum Einsatz kommt. :D


    Wie auch immer. Habt Spass.

  • the Picon path for Nuke.Evo is path="picon_220x132", so the folder isn't the usual "picon" folder, but "picon_220x132".

    ok thank you i only have to rename the folder i think time ago i had the same issue, but i didnt remember.

    And to choose the litttle picons on the left on channel selection i cant find in menu i think also i asked before but for other image


    thanks

  • Don't think too complicated ... ^^ Use for the primary picon base a 220x132 set. Then, instead of downloading (and maintaining) a second/third set, use symlinks to this 200x132 folder:

    Code
    1. ln -s /data/picon_220x132 /data/picon
    2. ln -s data/picon_220x132 /data/picon_50x30


    Each time if a sceen needs a 50x30 (or 100x60) picon, the 220x132 source will then be used (and scaled to the appropriated size).

  • ok perfect i was using the symlink for merlin image and doesnt works


    ln -s /media/hdd/picons/picon_220x132 /usr/share/enigma2/picon_220x132

    ln -s /media/hdd/picons/picon_220x132 /usr/share/enigma2/picon_50x30


    i think in my case should be like this:

    1. ln -s /media/hdd/picons/picon_220x132 /data/picon
    2. ln -s /media/hdd/picons/picon_220x132 /data/picon_50x30


    im going to test

  • ln -s /media/hdd/picons/picon_220x132 /usr/share/enigma2/picon or /data/picon


    &


    ln -s /media/hdd/picons/picon_220x132 /usr/share/enigma2/picon_50x30 or /data/picon_50x30

    cu


    DM 7080 SSSC @ OE 2.5 unstable
    DM 920 FBC S C @ OE 2.5 unstable

    DreamOne S @ OE 2.6 unstable

    Edited once, last by kid63 ().

  • It's stupid to use a hdd for picons. This will keep the hdd spinning all time and shorten its life. Picons either are stored in the flash (data) or on a usb stick.

    Gruss
    Dre


    Boxen (im Einsatz): DM920, DM900, DMOne
    Developer Project Merlin - we are OpenSource

  • Just compare you're paths and the defined ones. They are only remotely similar and can't work like that.


    Keep an eye on the correct names and subfolders ;)


    Edit: I'm now at the PC and can post the full path :)

    Correct: /media/hdd/picon_220x132


    So it is NOT picons/, /picons/picon_220x132, /picons_220x132, /Picon_220x132 etc. etc... It's not that difficult if you just read carefully :)

    so long
    m0rphU

    Edited 2 times, last by m0rphU ().