R.: I see many people suffering when starting on customization field. Some of them, leave custo for thinking everything too complex. Remember, you were a "noob" once too
R.: Why not take a look to THIS great tutorial made by neiio?
The process to installing themes are always the same. you`ll have success if follow that.
R.: Of course. Once you have a good idea, you can use WSB (Windows Style Builder) software to create your own. And please, share it to us.
A fantastic additional to you, when skinning your first themes is a complete tutorial made by Dave from virtualcustoms.net.
R.: Yes, you can do. I only ask a simple amount of U$400,00, donated in points here on dA - Nah, i'm joking. Not only my Visual Styles, but any of my skins are free to edit and redistribute. I really want to see the result and the proper credits.
R.: - Make sure you have your Windows patched with any of the UX patchers.
- Check for Windows Updates, and if available decide to install or not to install them.
- Stop Windows Update service from task manager when applying themes.
- Make sure you have required fonts that VS use.
R.: Get Resource Hacking software - ResHacker, Restorator..
Backup your x64 Explorerframe.dll located in C:\Windows\SysWOW64\ by copying and renaming to a batch file (.bat)
Open the .dll in Res Hacking software, then find the images and replace them
R.: Get CustomizerGod by Kishan-Bagaria
R.: To support Hi-DPI displays, skinners need to adjust HUGE amount of images, margins and properties. Change in DPI can even make some features unavailable. Thus, many of them don't support other than regular DPI settings in Windows. Keep in mind that DPI changes in Windows don't work like in OS X, as the scaling is different and not everything changes according to DPI. In short, most of the themes don't support hi-dpi setting unless stated.
R.: Windows Style Builder - easiest and safest way
Resource Hacking - troubling way of doing it, but still safe if you know what you're doing and don't screw up margins or images
SOME font settings can be edited by turning off aero and going into windows classic settings. These DO NOT include all fonts and you end up having a messy desktop.
R.: Download Windows 7 Aero Blur Tweaker by Kishan-Bagaria and disable Aero Blur. MAKE SURE you run aero though! You can check that by opening task manager and see if themes and desktop window manager services are running.
R.: You will need Windows Style Builder or Resource Hacker and registry editor or other way of changing the icons (Librarian tool, iPack, IconPackager, editing system dlls..) and a blank font file - you can find it in many themes or just google it man! First change icons to whatever you want. Then, find TreeView properties with your tool. If you are using Windows Style Builder it's in Explorer&Shell\Explorer\Tree View\Tree Item and change font to Blank. Save and apply VS, then move the sidebar right border all the way to the left to get same padding around icons on all sides.
R.: This was the first way to really customize Windows OS way back in Win98, however since both 7 and 8 support the shell it's still skinnable. To do this you'll need Jasmins 3D Color Changer, preferably a color picker tool or opened GFX software/vector GFX software, and Font Manager + Font Creating software (f.e. Font Factory). Using Jasmin's 3DCC you can customize colors of the shell UI. Use customization window from personalization to change the fonts - these are all you need in classic Shell. To customize caption buttons or other glyphs in classic Shell you need to edit Marlett font. Since Microsoft never finished it and it's a corrupted font regardless of what Windows OS you are using, make sure to back this one up! Then open it in any font editing software and replace the glyphs. Keep in mind that fonts use either bitmap or vector graphics so you won't be able to replace the glyph with regular png image. Best practice would probably be to use vector graphics software like Adobe Illustrator or Inkscape. In a very weird case you are doing it on OS X, Sketch.
R.: No. To use uppercase or lowercase you will need to edit font itself - PAY ATTENTION TO THE LICENSING.
R.: QTTabbar - Customizable & skinnable. Should work with x64 too!
Another app our friend KealiaLaw noted is Cover. Another interesting extension to ably tabs in your explorer.
Hints to use it: Just remember that Ctrl + T to open the page, and Ctrl + W to close the page, Ctrl + Tab to switch pages, the work efficiency far more than doubled!
R.: Sorry, but i can`t tell it yo you. each person has your abilities. but here goes some tips
- If you`re a photoshoper, XION Player will be awesome and pretty easy. XION Player uses your .PSD file to build skin and name of shapes of attributes.
Is a interesting way to skin
- If you`re a coder, two awesome options to you: Winamp and Foobar. Maybe the harder of the list
- If you like to use software to render your skin, the better choise is AIMP3.
R.: As I said, i recommend you skinning Foobar, if you`re a coder. You`ll need many line to get a good presentation.
Foobar uses components (.dll) to ably you do cool things. but you don`t need to have all them installed so, lets follow 3 tutorials for beginners made by Markkoenig, slowboyfast and FlipOut69
How to skin foobar2000 - Part 1
How to skin foobar2000 - Part 2
How to skin foobar2000 - Part 3
Jan Cairns wrote a simple but complete Tutorial. you can find it here. Is another good page to follow when starting.
R.: The first place to take a look, (for every application is the own forum. Winamp Forum have large content to help you in each step of your skinning process.
R.: After finished skin, select your skin folder, righr click and (having winrar instaled), go to "add to the file..." change the extension of file to ".wal", then Ok.
R.: Xion Player uses your .PSD file as skin. yes, you can do (almost) everything you want, if you follow the rules. Each layer Must have a specific name to work, or skin won't load.
I suggest you start modding some skin, you can use one of mine to try.
All controls and layer names you can find here.
R.: Editing AImp3 seams to be easy when you point he's the only player to has a skin editor. You can start from two different models there. Single skin or a windowed one. Is very fast to understand how the skin editor works
Unfortunately, after created skins, you can't edit it unless you have the project file. It means that modding skins are not allowed here. (you can ask to the author the project file)
R.: Yes, it is
R.: Aaron-A-Arts wrote a helpful journal step by step. Follow Aaron's letter
R.: First step is installing the software (uhh, really?). Grab it from Miranda NG site; Then:
- Check if you have and if not download the following plugins: clist_modern, tabsrmm, IEView, PopupPlus (optional). HERE the full list of plugins
- Download skin for any of the plugins. You'll have a large list here on DA
- Apply it through settings and customize it how you want in Options\Message Sessions, Options\Icons and Options\Contact List
- Ask author or any of the miranda skinners for certain option in case you can't find it
R.: Best way is to use clist_modern plugin and build from existing skin (although it's not that hard to make simple clist from scratch too). Clist_modern uses 2 types of images - regular image, and glyphs. While you can use regular images, glyphs are much more important as they carry the function and can change state, transform etc. At the beginning of clist skin, you load all your metadata, followed by loading images and glyphs you want to use. The basic premise for the loading process is:
$=Function=sGlyph,Image, VIEW FORMAT (f.e. Image), doge.png (your file), scalling (tilehor, tilevet, tileboth and same for stretch), Margins (4 values, 0,0,0,0), Alpha Channel (transparency)
For example a background image with size 100x100px with 10px margins:
After this, you need to declare skin rules. These control what the glyphs do. You can find whole list in clist_modern.dll (open with Reshacker or similar software). Here's an example for status glyph:
This gave the glyphs their proper ID and stated when they're shown. Now you need to actually display them on the clist canvas. Here's an example of that, a status glyph with 3 states that have the same image size and margins. Again information is in clist_modern.dll:
# statusmenu=sPush,CList/ShowStatusMenu,-15,-50, 15,-25,CBCB-,0,0,Set Status
Rules conclude the ModernSkin section of the .msf file, which is all you need to load your skin. Usually, it's followed by CLUI (client margins, which you can set in options aswell) and other client settings that can be set for user, but many of those properties are no longer known throughout the community, which is why your skin still has statusbar, menubar and hideously misplaced group indent despite the fact preview has not. You can change ALL of these in Options window. Some skins don't include these declarations so that user sets them as he wants and they won't be overwritten by applying the skin.
In the end, there's a CLC section, which skins fonts and colors. Don't even try to read it properly in text editor. Go to Options\Message Sessions\Fonts and Colors and change the values. Hit Export and place the exported code at the end of the .msf file.
And that's it! Now you got your contact list skin
R.: Tabsrmm is a skinnable plugin for Miranda that changes default UI to tabs view.
When checking out downloaded skin you will find out that it's made of a folder with images, a .tsk skin file and .tabsrmm theme file. Deep, freeform skinning is done using .tsk file, and .tabsrmm controls fonts and colors of the message session. In case you're using IEView, you won't need a lot of stuff in .tabsrmm theme, but it's still good to include them as they also control group chats and protocols with special stuff.
You can place your .tabsrmm theme directly into your clist_modern config aswell if you want. Tabsrmm is THE skinning Miranda plugin, and the hardest one to use. You can find documentation here, which is the best place to reference your ideas and code from.
R.: Don't worry about this plugin unless you have tabsrmm already set up and running.
Miranda conversation window is made from 2 basic parts - a frame with tabs, toolbars and similar things controlled by plugins like tabsrmm skin, and a container with displayed conversation, input form etc. controled by f.e. tabsrmm theme file.
IEView is by far the most popular plugin to skin, so there are lots of them. The template of the HTML file is available in it's dll similar to clist_modern, and you can check it on GitHub aswell. You can switch different IEView configs between protocols, or disable the plugin for some protocols too. There's also a "Compatibility Mode" you can use if you work with other plugins controlling the container, but it disables lots of options.