It’s not as hard as David Copperfield would like you to think it is.

How exactly do you create those criters? At first it may seem a tedious job but once you have all the frames, you’re pretty much set.

First thing I did in my research was asking the experts. I’ve asked some of the skin authors and most of them uses a kind of workaround to this. The most detailed explanation I’ve received from one of the greatest WindowBlinds skinners – Mike Bryant:

and why doesn’t it happen automatically

There was a concern by some users why SkinStudio shares a start menu with the original substyle when you create another substy;le based on it..

Basically the answer is – It’s not a bug – It’s a feature. It’s like that by design. If you select a prefix on save then you will get another start menu as well, otherwise skinstudio will use the same stuff for 2 reasons.

it does not know how to name the new “xpstuff.xp”.

it does not know whether you really want to break the connection. You may as well want to just make a variation of your skin with slightly different titlebar buttons.

But imagine it did that so 2 things happen – you didn’t specify the prefix to create new images so once you change the images in one substyle you change them in the other too since you didn’t tell it to make copies of them. Now imagine how outrageous it would be. “But it uses another xpstuff.xp” you would say. “Why one substyle breaks the other substyle images” you would say. And you would be right. if everything’s duplicated then everything is duplicated, if nothing then nothing.

Now let me show you the solution to the problem. I usedto direct people to the “Code” tab forgettig that the combo for “non image” file references is actually editable. But today I’ve read an easier sollution, by Tiggz:

When you want the substyle to have a different start menu, after you create the new substyle you need to click “taskbar” in the navigation tree in the left hand side of the window, then over on the right click on the word file, and then below, in the “value” text entry field you can change the name from the default (XPStuff.xp).

Are there no limits to customization?

Very important: Recoloring or skinning icons does not change the original author’s copyright, nor does it make such icons yours. If you recolor or skin an icon that has not been made by yourself you may not upload or share a recolored icon without the original author’s permission.

In the next few days Stardock is publishing the next component of it’s extremely successful ObjectDesktop. The new component is called IconDeveloper – the tool’s , I’m the developer of, main purpose is to make it easy for casual users to create icons and make it faster and more efficient for professional icon artists to do their work. Celebrating the event I decided to write a short article about going really crazy with icons and how to do it with IconDeveloper. What skinning means (but is not limited to) is changing the look of certain part of applications. The article will describe how you can change the appearance of an IconPackager theme or an Icl file (Icon library).

So you recolored your icons already? (If not checkout the article about mix matching your themes with your skins – the functionality described there is now a part of IconDeveloper). But it still isn’t enough? Why stop on recoloring? Why not make your icons exactly how you want them to be? Why not SKIN THE ICONS?

But since I’ve done the recoloring already, should I stop there? Let’s open the modded “PixOs Toxic”…

Select a new name for skinned theme and specify that I want to actually “skin” it…

Now what can we do here… I know! Let’s set it on fire!

Or make it suffer in a really polluted environment… sorry Paul

and actually make it ultimately match my skin of choice… and a bit smoked (Why? Why not?!). To do this I’ve had to edit an image from the Visual Style to create a bevel I can now use as a background (made for sake of this artticle only). You can actually use any image for either a background or overlay – just press the “Browse” button and select the image you want to use.

The possibilities are countless. IconDeveloper comes with a number of backgrounds and overlies for you to toy with, but the real potential is in your creativity. Make your own icon’s skins. The sky is the limit!

Could we have some decency here?

There’s a lot of noise in the news sites (Slashdot.org, News.com and Neowin.net) about the Monday release of Konfabulator for Windows. But to be honest they just make me think that journalists today no longer care to be through and accurate and will chew in everything that a PR department will send them. I do not personally rant about those kind of things, but this one got me going. Especially one thing Mr Alro said which is cited in about all of the sources:

‘When you have a great idea, you want more than 2 percent of the global market to have access to it.’

That’s just utter gibberish!

Unless you lived in a glass castle for the last 6 years or never been a part of the desktop customization community you know that there already is a pretty stiff competition in that area on Windows. He sounds as if some Macintosh saviours bring the desktop customization into the abandoned wasteland of Windows.

Hellooo! I have a news for you! DesktopX is at least a few years older than Konfabulator and it has always been a Windows application. And it just began from that. There are multiple desktop customizing apps epart from that, Kapsule and AveDesk to mention just a few of them.

Unfortunately this is not news for Mr Arlo Rose he is pretty aware of it as I’ve been reading his rhetoric after Apple anounced Dashboard in Tiger and that just makes me all much more astonished about this statement.