[Guide] An Introduction to Iconres-Skinning

Dieses Thema im Forum "Motorola FAQ und Anleitungen für Fortgeschrittene" wurde erstellt von InsecureSpike, 6. Mai 2008.

  1. InsecureSpike

    InsecureSpike VIP Mitglied

    Registriert seit:
    31. Okt. 2007
    Beiträge:
    72
    Zustimmungen:
    1
    NOT TO BE REPOSTED, WITHOUT PERMISSION


    An Introduction to Iconres-Skinning

    Skinning for the V8, Z6 & U9 is very different to skinning a standard Moto,
    and with some hard work some really impressive Skins can be made,

    when a skin folder is opened you will see there are 2 types of files & a jpeg image,


    [​IMG]

    iconres.ezx;
    The iconres.ezx is more like the dat files of a P2K skin and the CG15 (DRM),
    all those images are stored in the iconres.ezx, there could be 1976 - over 2000 icons and images,
    in an iconres.ezx,
    this certainly looks daunting, as all of the icons & images are in one file,
    although this is so much easier, in the long run
    so with every skin you can have a matching DRM, cool!!

    not all iconres.ezx files contain DRM icons,
    the Stock Alkali skin contains skin & drm icons & images,
    but the Stock Indium skin has just the skin images,

    if you just want to make a skin and use the stock DRM, just leave out the the DRM files,
    you also could just make a DRM, by leaving out the skin images,
    the only problem is that, the missing icons will be replased by images from the default iconres.ezx,
    which is found in the CG52, usually the Stock iconres.ezx is the Alkali skin.
    In the end any icon or image left out of the iconres will be replace by the icon in the default iconres.ezx



    The Tools

    there are 2 new skinning tools for the opening of the iconres,
    as skinner4moto will not open these files,

    kview;-
    isn't very good as it will open the file but will not repack it properly!
    there are a few bugs including calender and calculator errors.
    (i use this tool to edit an iconres, add single, multiple or all of the icons, so doubles don't get created)
    Remember:
    this tool cannot open a iconres that has been compiled with the MotoLinux Iconres Composer!!

    [​IMG]

    MotoLinux Iconres Composer;-
    this is the tool that i use to compile a test iconres or a finished one,
    there are no repacking bugs,
    but i do stress to be careful when replacing icons with this tool, as doubles can be created!!

    [​IMG]


    Both tools will open the iconres, and with both you can extract the icons,
    in the stock iconres files there are 2 types of files BMP and GIF files,
    in kview you can have the choice of extracting BMP or PNG,
    but it messes up the PNG icons, as it doesn't work transparencies very well,
    this is where i use the iconres composer, to unpack the icons/images as BMP,
    then i use a Batch Converter to convert ALL the BMP's to PNG
    (i personally change all of the BMP files to PNG files just easier for me to edit)

    once you have unpacked an iconres, and looked in the icons folder,
    you'll see that all the icons inside have short names, and are not numbered,
    which makes it easier to find out what the icons are and what they do,
    as their name states what they do,



    Now here is how i go about making a iconres.ezx,



    Part 1

    Open a stock iconres using the Iconres Composer,

    [​IMG]

    then split it,

    [​IMG]

    this will make a folder in the same folder as the opened iconres,

    [​IMG]

    next make a new folder and call it New-Icons, then move All of the Gif icons to the new folder,

    [​IMG]

    so that in the old folder there is only the BMP icons & images,

    Next batch convert ALL of the BMP files to PNG,
    so that all the backgrounds are now transpartent,
    and then all of the converted PNG's go into the New-Icons Folder,
    (and throw all the left over BMP icons and images in the trash as we dont need these)

    [​IMG]

    Now back this folder up, as a RAR or Zip,
    Just in case one of the stock files is need again, or for when a new skin is started,

    Now the editing can start, choose an image editor of your choice,

    The skinning much easier if i tackle the DRM icons at a seperate time to the skin images,
    As it's very easy to get lost sometimes, (especially if your new to this type of skinning)



    Part 2



    Once all the editing is done, start k-view,

    [​IMG]

    click on settings & uncheck the Use iconres.dat box then click ok,

    [​IMG] [​IMG]

    Open up any Stock iconres.ezx using k-view.

    [​IMG]

    [​IMG]

    Now once k-view has opened and split the iconres.ezx you'll find:
    2 new folders, an icons folder and a raw folder, also
    theres 2 new files a iconres.hdr and a iconres.dat,

    [​IMG]

    Open the icon folder and select ALL the icons, then throw them all in the trash!

    Now move all the icons and images in the New-Icons folder over into the empty icons folder, that kview made
    Next make the iconres by saving to EZX.

    [​IMG]

    Ok this iconres is ok to use but has bugs, (but needs to be kept for re-editing)
    So start the MotoLinux Iconres Composer, and open the New iconres that's just been made,

    [​IMG]

    first i make another folder, and name it Iconres'd as this is where the New iconres will be saved,

    Next press save, and navigate to the iconres'd folder and save in there,

    [​IMG]

    ok this new iconres can now be tried on yer V8, Z6 or U9.


    Now a you have a custom iconres.ezx


    Part 3

    usually some more editing is necessary,
    now the iconres.ezx made with the MotoLinux Iconres Composer, cannot be opened with k-view,
    this is why i always keep both iconres.ezx's,
    if i need to change something, i open the folder with the split Stock iconres
    and i pull out the icons folder that has the new icons in, and re-name it,
    then delete everything, (raw folder, iconres.dat, iconres.hdr and the iconres'd folder)
    except the iconres made with k-view,

    then edit the icons and or images needed, and repeat part 2


    simple as that!!!



    Special Thanks

    Rasputin007 & FLdodger for beleving in me!!!!!

    MotoLinux Iconres Composer - Meiner Einer and Big Granu @faq4mobiles

    K-view - lucrece

    i cannot for get All the guys who've beta tested for me;

    Rasputin007, FLdodger, WildCard26, O.M.G, Psycomorpher, Protector, SuperJoker, TomDunne21 & Vijushimpi.

    and the girls;

    Bikki, Stephuhnator & Toots



    NOT TO BE REPOSTED, WITHOUT PERMISSION
     
    #1 InsecureSpike, 6. Mai 2008
    Zuletzt bearbeitet: 6. Mai 2008
    bugbugbugbugbug gefällt das.
  2. Meiner Einer

    Meiner Einer Vertrauensmitglied

    Registriert seit:
    21. Aug. 2006
    Beiträge:
    5.745
    Zustimmungen:
    15
    WOW...

    Great Guide!
    Thanks for sharing.

    PS - Kview is written by "lucrece" from motofan.ru
     
  3. InsecureSpike

    InsecureSpike VIP Mitglied

    Registriert seit:
    31. Okt. 2007
    Beiträge:
    72
    Zustimmungen:
    1
    thanks mate,
    and thank you for the MotoLinux Iconres Composer

    post updated....
     
  4. J4ZZ

    J4ZZ VIP Mitglied

    Registriert seit:
    9. Sep. 2006
    Beiträge:
    508
    Zustimmungen:
    1
    Kann mir jemand sagen, warum das so ist?

    Das Problem mit den *unk files die nur text enthalten ist ja bekannt, bei diesen Iconres files scheitert allerdings auch kview 0.52 und nicht nur der Composer. (der alte kview 5 entpackt diese "seltsamen" iconres files allerdings)

    Gruß,

    ..::J4ZZ::..
     
  5. Mæz

    Mæz Guest

    Holy Crappamoly !!!!...... :D

    Thanx InsecureSpike for this guide...... that makes skinning easier.......
     
  6. Meiner Einer

    Meiner Einer Vertrauensmitglied

    Registriert seit:
    21. Aug. 2006
    Beiträge:
    5.745
    Zustimmungen:
    15
    @ J4ZZ
    Wieso erfahren wir (BigGranu und ich) nichts davon? Könntest Du bitte mal eine solche Iconres uppen zum testen und anpassen des Programms? Schließlich haben wir das .css ja auch nachträglich mit aufgenommen.

    Der Composer erstellt doch korrekte Iconres's - oder etwa nicht?
    1. Mit Markteinführung der V8/Z6 und jetzt U9 wurden von Moto auch 32 Bit RAW verwendet. Das Problem würde also auch mit einer originalen iconres auftreten, die sowas enthält.
    2. Der Composer wertet die interne Tabellen vollständig aus und berechnet sie auch komplett neu. Oder "brutal" ausgedrückt: Man sollte sich nicht darauf verlassen, das die Erde eine Scheibe ist...:D
     
Die Seite wird geladen...