First Previous Page 136 of 175 Next Last

Changing icons on Windows Vista

Giving your desktop your own style

Wednesday, April 18, 2007 by Frogboy | Discussion: IconPackager Talk

Windows Vista has some awesome looking icons.  Microsoft went way out of its way to try to give Windows Vista a truly polished look.  They did this by giving most icons a 256x256 icon.  Think about how large that really is. Each Windows Vista icon has an image of that resolution.

But as good as they are, what if you want to change them? How do you do it?  Windows Vista maintains the ability to change the icons of individual short-cuts and folders though in very inconsistent ways.

The best, easiest, and to my knowledge only way to change Windows Vista icons all at once is with Stardock IconPackager. With it, users can change individual icons or change all their icons at once by applying a "package" of icons to their Windows Vista system.  IconPackager even supports the new "live" folder previews.

Individual Icon Changing

IconPackager adds a context menu called "change icon" for most types of files that looks like this:


Changing individual icons with IconPackager installed

 

Once IconPackager is installed, this functionality is natively added to Windows Vista. It's totally seamless.


Any icon that doesn't have a 256x256 image gets a smaller version that doesn't look as good as it could

One issue on Windows Vista is how icons are displayed. Most icons are 32x32 pixels in size. Some programs have a higher resolution 48x48 version.  But on Windows Vista, unless there's a 256x256 version, the lower resolution version is displayed in it native size which can look strange (especially on your desktop). 

Users of Windows Vista will no doubt soon notice that as they install programs that add short-cuts to their desktops that many of those icons look smaller and strange compared to the default icons on the desktop.

IconPackager supports changing program icons as well.  To do it (once you have IconPackager installed) right-click on the icon you want to change and choose properties.


Program icons can be changed with IconPackager installed as well.

Packages of Icons

The entire set of Windows icons can be changed in a single click by using an icon package. There are thousands out there. Most do not yet support the 256x256 resolution of native Vista icons yet (Stardock is working on a way to up-convert on the fly if there's a sufficiently high resolution version available).  But all the icon packages that come with IconPackager include full Windows Vista support.


The IconPackager application

Changing your icons is a pretty straight forward process -- choose the icon package you want, load it, and hit apply. Within a few seconds, nearly all your icons will be changed.

More Screenshots

Getting IconPackager

IconPackager is a free download. You can get it at www.iconzone.com (or https://www.stardock.com/products/iconpackager).

 

New Vista Icons

Windows Vista Changes How Icon Customization Works

Tuesday, April 17, 2007 by Zoomba | Discussion: Icons

Windows Vista has a lot of little visual tweaks and changes versus it's older sibling, Windows XP.  Where XP's icons are simple and straight-forward in their design and presentation, Vista's icons require more design work, and have a bit of technical flash to make them fit in with the rest of the improved visuals of the recently-released operating system.

In Windows XP, icons are typically a maximum of 128x128 pixels, with most people viewing them at 32x32 size on their desktop.  If you wanted to change the size of your icons, you had to dig through preference windows and dialogs to try and manually set the sizing.  Sure, there were a few preset views (large icons, small icons) but those didn't give you a great deal of choice when tweaking your display.  There's also no dynamic scaling.  So you can't easily/quickly test icon sizes on your screen to see how they look.  Add to this the fact that many applications don't necessarily have high-quality larger icons defined in their .ico file (this is especially typical of shareware type software, or older apps from the Win9x/2k days) so if you run with higher icon sizes, some icons look gritty, pixelated and down-right ugly.  Woe to the person who has a very large monitor or poor eyesight.

Of course, there's a certain benefit to how icons work in XP, you have a few preset sizes you have to worry about, anything else is something strange only a handful of users would every try anyway.  So as an icon artist, your life is just a little bit easier.  16x16, 32x32, 64x64 and 128x128 are all you need to hit 99% of what users will try/see.

Now there's Windows Vista.  Vista not only takes icons up to 256x256, it does dynamic icon scaling, adds dozens of new system icons for icon package artists to design for when creating new themes, and adds a completely new type of icon; the Live Icon.  These changes present a completely new set of challenges to artists trying to make complete system icon packs, or for ones looking to update their XP pack for Vista.  First, lets look at the dynamic scaling.  While there are still a few presets for users to click through, there's also a convenient slider in the view menu that will, in real-time, alter the sizing of any icons on your screen.

Icon scaling is a nice feature that will make life much easier for those of us with either poor eyesight, or impossibly huge monitors.  Vista's icon scaling also is done per-window, instead of across-the-board like in XP.  In XP, you set the icon size once, and that was the size across every single window you opened.  In Vista, you set icon size independently in every window you open, and even on the desktop.  This level of built-in choice is nice for users who only have a few very important icons on their desktop, and for usability purposes want those to be large and easy to spot, while keeping other icons on their system small and neat,

Possibly the coolest icon change in Windows Vista is its support for the display of "Live Icons" when browsing through folders. If your files have an appropriate thumbnail handler, you'll be able to see a richer preview of the file in question as opposed to just a static icon set by type.

This support is also present when viewing subfolders in an Explorer window. For instance, if you have a subfolder filled with images, the Live Icon support will attempt to show the first couple as part of the folder icon to give you an idea of the folder contents.

On top of scaling icons and live icons, Windows Vista throws a lot of new items into the mix that you now have to build new icons for.  Artists who tried to theme out even the Control Panel icons for XP will find that not only have many of those Control Panel items changed, but there are also more than a handful of completely new ones to make icons for now.  Windows XP has roughly 30 Control Panel icons on a default install.  Windows Vista Ultimate?  53.

With this brave new icon world stretching off into the distance, there comes the question of tools for both the artist and the user.  Customization junkies that are making the leap to Vista no doubt are looking for the same level of control they enjoyed with Windows XP.  For artists, the world of tools is much like it was just a few short months ago.  Tools such as Eclipsit's Microangelo Toolset 6, Stardock's IconDeveloper, and IconWorkshop from Axialis still exist and work just fine for creating all the new icons needed for Windows Vista.

On the user end, it's a little more difficult to find software that lets you switch out your icons for something newer and cooler looking.  By default in Vista, users technically have the ability to change every icon they use by selecting them individually, digging through their properties and changing them one by one.  A step up from that comes with tools like Microangelo Librarian which let you change them out with simpler to follow menus.  However, if you want to completely switch out your icons and replace them with completely new Windows Vista icons, your only option on the market is Stardock IconPackager, which added full support for Windows Vista and Live Folders in version 3.2.  IconPackager lets artists bundle their icon sets into one easy to use file, and users can substitute in that entire set, replacing all of their main Vista icons with just a few simple clicks. 

Live Icons, real-time scaling of icons on the desktop, and numerous altogether new icons make Windows Vista a new and interesting challenge for both artists and users.  Just another example of some of the cool new opportunities presented by Vista.

Note:
If you're interested in seeing how the Live Folder Icons go together, we have a set of template images for you to take a look at when building your own icons for Windows Vista.  Grab the example files here.

WindowBlinds: Manage Your Desktop Wallpaper

Walkthrough of WindowBlinds Wallpaper Features

Monday, April 16, 2007 by Island Dog | Discussion: WindowBlinds

I recently wrote about the ability of WindowBlinds to change the color of your visual styles, so this week I wanted to touch on another cool feature of WindowBlinds which is the built-in wallpaper changer.  If you are like me, then you probably have a large gallery of wallpapers on your hard drive.  Organizing them isn't always easy, and finding them and adding them to your desktop can be just as tedious. 

Fortunately, WindowBlinds has some features that can help you with managing your wallpaper collection.  In this article I am using WindowBlinds 5.5 to demonstrate these features.  In your WindowBlinds configuration window select "Change my wallpaper" from the menu on the left side. 

You can simply browse through the thumbnails, and when you want to apply a wallpaper, just double-click the preview and your wallpaper will be applied to the desktop. 

There are two options near the bottom right on the configuration window just above the thumbnail previews.  The first one will change the wallpaper between the larger preview and a gallery view.  The second image (tools icon) is the wallpaper settings option.  From that screen you can add/remove folders that include wallpapers, and select/deselect those folders from viewing as well.  Simply click "add folder" and browse to the folder that contains your wallpaper collections and they will be added for viewing in WindowBlinds. You can also set the wallpaper options such as tiled, centered, stretch, or smart mode from there.

Now that your wallpaper collections are set up, click "Changer" to configure your wallpapers to change based on certain settings.  You can set WindowBlinds to change your wallpaper on Monday mornings, every morning, at every logon, or every hour.  These are optional settings and you can set it to never change your wallpaper with those settings.  You can also set these to only use the wallpapers of your choice, or apply it to them all if you like.

Now a quick note for people who don't want WindowBlinds to apply wallpaper that is included with a theme they are using.  In the WindowBlinds configuration select "Override default settings", and make sure the setting "Apply the wallpaper included with a skin" is unchecked.

I made a short video to go along with this tutorial.  It shows how easy it is to manage your desktop wallpapers and goes through the features described in this guide.



Video: WindowBlinds: Manage Your Desktop Wallpaper

Creating 'Shell Animations' for SkinStudio Part 1

Creating AVI animations in Flash tutorial Part 1

Saturday, April 14, 2007 by Life is a Game | Discussion: WindowBlinds Tutorials

A week ago I have posted a 4-day series of articles that you describing my progress of creating my 1st WindowBlinds skin. You can view articles WWW Link here and download the skin WWW Link here. In one of my articles ‘unclerob’ asked me to create a tutorial on how I created the animations for my skin. It seems that this month will have for me more 1st time experiences then just a WindowBlind skin as I decided to post my 1st tutorial on WinCustomize.com.

I used Flash to create the animations because I’m quite skillful with it as I’ve been using it since the Flash 5 release 6 years ago and it’s really easy to draw and animate graphics. OK, enough talking let’s get started. You can download the source file used in this tutorial WWW Link here.

--------------------------------------

STEP 1
First create a new document and then click on size option (1) and ‘Document Properties’ window will open where you enter the title (2), set dimensions to width 272 px and height 60px (3), choose the background color of your animation (4). Make sure it matches the color of the background of your dialog windows. Finally set the frame rate (5). I recommend the rate of 10 frames per second.



-------------------------------------

STEP 2
Next we need to create layers where we will create some objects later. In this tutorial we will need 3 layers as Flash animates all the objects in the selected layer. So we have to make sure that the objects that we want to animate and the ones we don’t are not in the same layer. Create layers by clicking on the ‘Insert Layer’ icon (1) and rename them for reference into ‘background’, ‘animation’ and ‘foreground’ (2).



-------------------------------------

STEP 3
Now that we prepared the document and layers we the fun begins. First click on the ‘foreground’ layer to tell Flash that you want to draw and object in this layer (1). Then select the ‘Rectangle Tool’ (2) and the properties window will show the below options (3). Choose the stroke color and thickness and the fill color to suit you. Finally draw an object (4).



-------------------------------------

STEP 4
Now we will ‘skew’ the object downwards to create the feeling of an open folder. Select the ‘Free Transform Tool’ and double-click on the fill of the object to select both fill and stroke. Finally position your mouse cursor on the right-edge of the object and click-hold and pull it downwards a bit and release it (2).



-------------------------------------

STEP 5
We also need to add the back cover of our folder. Click on the ‘background’ layer (1) and repeat the steps with the ‘Rectangle Tool’ (2) and ‘Free Transform Tool’ (3) from the STEP 4 and now your folder should look something like this (4).



-------------------------------------

STEP 6
Next we need to duplicate the folder to the other side of the document. To do that you need to select the folder with the ‘Selection Tool’ (1) and draw a rectangle around the folder to select both front and back cover (2). Finally press and hold ALT and then click and drag the folder to the other side of the document and release the left mouse button followed by the release of the ALT key. I recommend to hold SHIFT while dragging to make sure both folders are aligned.



-------------------------------------

STEP 7
Now we will ‘mirror’ the duplicated folder. If you have deselected the duplicated folder repeat selection method from the STEP 6. With the folder selected open the ‘Transform’ panel (1) and make sure that the ‘Constrain’ option is switched off. Finally add a - in front of 100.0% (3) and press ‘Enter’ to apply changes and Flash will mirror your folder (4).



-------------------------------------

STEP 8

If you are happy with your folders lock the ‘background’ and ‘foreground’ layers to make sure you don’t move them by mistake while working in the ‘animation’ layer. You can lock layers by clicking on the black dot in the ‘lock’ column (1) and (2). Dots will turn into small locks when clicked to show that the layer is locked for editing.



-------------------------------------

STEP 9
Now we need to create an object that we will animate moving from the left to the right folder. Click on the ‘animation’ layer (1) and create an object with ‘Rectangle Tool’ (2) method that we used in the STEP 3. You can either create more objects in it or as in this tutorial add some text (4) with the ‘Text Tool’ (3).



-------------------------------------

STEP 10

Now we need to insert the amount of the frames we want to create for our animation. I recommend 35 frames for your animation. Before inserting more frames move your object with the ‘Selection Tool’ inside of the folder (2). To insert frames click the 35th frame of each layer (3) and press the ‘F5’ key to insert frames (4).



-------------------------------------

STEP 11
Now we will convert our object into ‘Motion Tween’. Right-click anywhere in the timeline of the ‘animation’ layer (1) and select the ‘Create Motion Tween’ option from the drop-down menu (2). Finally select the last frame of the ‘animation’ layer and press the ‘F6’ key to insert a keyframe.



-------------------------------------

STEP 12
Next we need to determine the final position of the animated object. To do that click the last frame of the ‘animation’ layer and move the object with the ‘Selection Tool’ (2) to the desired location (3).



-------------------------------------

STEP 13
And now the moment we’ve all been waiting for… Press CTRL+ENTER to ‘Test Movie’.



-------------------------------------

STEP 14
If you are happy with your animation you should export it to AVI to use in SkinStudio. Go to File>Export>Export Movie. In the ‘Export Movie’ window type in the ‘File name’ (1) and choose the ‘Windows AVI’ from the file type menu (2) and press ‘Enter’ key.



In the next window you will see the settings for exporting to AVI. Make sure that the ‘Width’ and ‘Height’ are 272 and 60 (1) and that ‘Maintain aspect ratio’ is on (2). For video format I recommend 16 bit color (3) with both ‘Compress video’ and ‘Smooth’ options turned on. Finally choose ‘Disable’ sound format (4) as our animation doesn’t contain any audio and click ‘OK’.



In last Export window you will be able to adjust the compression options. You can test a bit different codecs and compression options but I recommend to use the ‘Full Frames’ compressor for best results (1).



There you go we have created an AVI animation for the SkinStudio in Flash. We used only basic animation options in this tutorial. Flash comes with lots more effects which I will cover in my next tutorial. The exported animation created in this tutorial looks like this. Please note that the actual exported AVI is better quality then the below exported GIF.

This Week in Skinning - April 13th

Skin Roundup for 4-13-07

Friday, April 13, 2007 by Island Dog | Discussion: Community

We are just about halfway done with this month, and it's been pretty good so far. The holiday seemed to have slowed things down a bit, but submissions are rolling in and it's shaping up to be another great week.


I'm seeing some activity in the ObjectBar section again, and it's always good to see some new submissions in a category that is sometimes lacking.

Let's get to the picks!



Splash Orange for Bootskins
by Life is a Game

Splash Orange is definitely different than your standard XP bootskin, and that's a good thing. Sometimes it needs a little color, and Life is a Game has accomplished this and has a few different versions with different colors, so check out his gallery for more.

Download





Circles in Dreams
by Hyszz

This Dream has received a lot of attention in the past couple of days with good reason. It might seem like a simple idea, but it looks really good on the desktop. This is one animated wallpaper you need to check out.

Download




Old Ironsides in Wallpapers
by kenwas

Another beautiful creation. This wallpaper speaks for itself so it's best for you to download it and try it for yourself. Great work.

Download





Black in WindowBlinds
by tehZERO

This is a fantastic WindowBlinds skin that is clean, and has a great use of transparency. This is one you need to download.

Download











Neutronium DM in WindowBlinds
by I.R. Brainiac

This is another skin that speaks for itself. It's hard to describe, but I'm pretty sure you won't be disappointed with this one.

Download











Don't forget to e-mail with your suggestions and picks for featured skins. Your comments and suggestions are always appreciated. Also remember to keep the community updated with our "What are you working on?" thread in the forums. Great job to everyone and see you next week!

Learning DX Step-By-Step - #6

User Input / Save / Retrieve

Wednesday, April 11, 2007 by RomanDA | Discussion: DesktopX Tutorials

Step-by-Step Tutorial

#6 - User Input / Save / Retrieve

A series by RomanDA

Listing of other DX Tutorials: Click here
Today's Lesson: "User Input / Save / Retrieve"

In this lesson we will cover how to gather information from a user via a popup dialog box, and to how to store and retrieve this data from the registry.

As in the previous tutorial, the goal here is for you to learn how to create an object, add code to it, and be able to edit that code to make changes to the way the object/widget behaves. The code is provided for you to copy/paste, but it would work best if you type in the code, to see how DX "Auto-fills" the info as you type. Its really the best way to see how DX works.

In order to use these Tutorials you will need to purchase DesktopX for $14.95 from Stardock.

Lets get started.

STEP 1 - What are we doing here?
Why do we want to get input from a user?
Well that's all depends on the gadget/widget you are creating. For a Weather widget you need to get the City code or Zip code to use. If you have a "to-do list" widget, you would want to get the item they want to add into the list. There are a lot of reasons you need to gather input from the user.

Why store the data in the Registry?
I have picked using the Registry over using the built in functions because I have had issues with them not working 100% and they only work when you run it as a widget/gadget not in "builder" mode, and we want to see how this works. A lot of people do not like to send things to the Registry but I have not had any problems with this, some people have told me they needed to "allow" the program to write to the Reg, but after that it worked fine.

Alternatives:
You can store data in a TEXT file, an INI file, or even an XML file. Just about any place you want to store things. The problem with this is that you need to know the location of this file on the user's computer. This can cause problems, but there are a lot of widgets that use this method. I have used it as well, there are ways to cope with trying to locate the file. Not something I'm going to get into on this tutorial.

STEP 2 - Lets Get Started- Make a TEXT object.
As in the previous tutorials, I think you should know enough by now so that i can move past the every-single-step process.

Create a TEXT object.
Add the text "Click to Add Text"
Then pick the font/color/size that works best for you.
Once that is all done lets add a VERY simple script to allow you to ask for some input, and quickly show that info.

ADD the following at the bottom of the existing script items (Object_OnScriptEnter/Object_OnScriptExit)

Function Object_OnLButtonUp(x,y,dragged)
If dragged = False Then
x = InputBox("Please Enter A Piece of Text To Add to " & vbNewLine & object.text , "Add Some Text")
If x <> "" Then object.text = object.text & vbnewline & x
End If
End Function

Lets break the above apart.

Function Object_OnLButtonUp(x,y,dragged) This line creates a FUNCTION that is called when you RELEASE the "Left" Mouse Button, IE: when you click your mouse.
The X/Y/dragged are used to determine if you DRAGGED the mouse when you went to click the mouse.
If dragged = False Then we use this so that it wont activate the function every time you MOVE/DRAG the item around the screen.
Meaning, if the object is not dragged then run the function.
x = InputBox("Please Enter A Piece of Text To Add to " & vbNewLine & object.text , "Add Some Text") X is the variable we want to store the data into.
The INPUTBOX is used to prompt the user for "input".
the format is inputbox(message,title)

We are putting in a message:
"Please Enter A Piece of Text To Add to "
(existing text here)
Then we have a TITLE called "Add Some Text"
If x <> "" Then object.text = object.text & vbnewline & x If X <> "", which means if there is SOMETHING in the variable X then take the object.text and add the existing object.text and X to make a new piece of text.
the vbnewline puts a NEW LINE or linefeed after the existing text.
This will basically add the text the user inputs to the next line under the Existing Text.
End If
End Function
End the IF DRAGGED...
And end the Function.

The way this will work is very simple.
The original Text object shows:
Click to Add Text

When you click on the object you will see a dialog box like below:


Then you put in your text that you want to add "2nd Line of Text"

The next Object will now look like:

Click to Add Text
2nd Line of Text

You can keep adding more and more lines to the object.

This was simply to show you how to get "input" from the user.
The next step will be to take this data and store it somewhere.

STEP 3 - STORING User Entered Data
Using the same style entry box above we want to store a single piece of data into the registry.
To add this to the registry, we need to create a link into the Registry by using the WScript.Shell, we open a link.
Then we use the .REGWRITE command to send info to a particular part of the registry.

In this case we are going to use the "KEY" you see listed below. You could use just about anything.

The HKCU = HKEY_Current_User - you could use HKLM - for Local Machine. I prefer to use the Current User because this way each person could have their own settings on the machine.

As for the rest of the key, that is open to your desire, for now we want to use \Stardock\DesktopX\Widget\Tutorial6\SavedInfo

This can be done right in the previous code like this:


If x <> "" Then 
  object.text = object.text & vbnewline & x
  Set Sh = CreateObject("WScript.Shell")
  Sh.RegWrite "HKCU\SOFTWARE\Stardock\DesktopX\Widget\Tutorial6\SavedInfo", X
  Set Sh = Nothing
End If

This Just adds the value of X into the KEY "Saved Info".
Of course every time you run this it overwrites the info with the next piece of text you put into the INPUTBOX.

It would not look like what our text.object looks like now. So if you want it to match the widget's info with what you are storing in the registry just change the RegWrite line and replace the X with object.text

If we click on the widget, and add the "2nd Line of Text" to it, then we look in the registry we see the following in the KEY:



You can see the KEY at the bottom of the REG Editor, and see the value stored in "SavedInfo".

If you continue to add things, you will see this change, over and over.

STEP 4 - Retrieving the Data From the Registry
So, we stored the data into the Registry, and into the actual object (kind of dumb to do it in both, but it helps us see what's being stored).

Now we want to pull that data into another object. So lets make a new TEXT object, put in the text "Click to Restore" (you can save a LOT of time by "right-clicking" on the existing object and hitting "CLONE". This makes a duplicate object with all the same code already in place!)

We want to add a very simple script to this object.

Function Object_OnLButtonUp(x,y,dragged)
  If dragged = False Then
   Set Sh = CreateObject("WScript.Shell")
   On Error Resume Next
   X = Sh.RegRead("HKCU\SOFTWARE\Stardock\DesktopX\Widget\Tutorial6\SavedInfo")
   Set Sh = Nothing
   If X <> "" Then object.text = x
  End If
End Function

You will notice about 80% of this is the same. What is different is:

 On Error Resume Next
 --- This is used to keep the program working if the registry entry doesnt exist.
 X = Sh.RegRead("HKCU\SOFTWARE\Stardock\DesktopX\Widget\Tutorial6\SavedInfo")
 --- Pull the data from the KEY and store it in the variable X
 If X <> "" Then object.text = x
 --- In this case we want to make the entire Text object match what we stored
     in the registry key.  But we also want to Make sure that there was
     something in X from the registry.  Thus the "IF".

You could make a lot of modifications to this one, but it has a great base to build from.
An option would be to make a "function" or "SUB" that does the load and store.

CONCLUSION
There are a lot of usages for these items. Anytime you want to get user info, or store/retrieve data from the registry you now know what to do.

Keep in mind that you can read in ANY "KEY" from the registry, so you could easily modify this to pull in the data in the key for say... Who the "Registered Owner" of the pc is

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RegisteredOwner

There are lots of things you could pull from the reg. and update as well. SO PLEASE PLEASE PLEASE Take care when you write to the registry.

Check back as I add new Step-By-Step Tutorials on how to make this a link to a folder, web-site, or just about anything you want!

I hope you have enjoyed this step into DX, and look forward to the next installment.

Enjoy,
RomanDA
http://romanda.wincustomize.com

This Week in Skinning - April 6th

Skin Roundup for 4-6-07

Friday, April 6, 2007 by Island Dog | Discussion: Community

I can't believe it's Friday already, where has the time gone? Well not too sure, but it's time again for "This Week in Skinning", and I hope you got a chance to check out the newest regular feature, "This Month in Dreams". The feedback was great and I appreciate the comments I received.

If there is any suggestions or features you might like seen, always feel free to drop me an e-mail or PM. Now off to the picks!

Philo for CursorXP
by Richard Mohler

Richard has created a nice, clean cursor that fits great with many themes. Nice work!

Download






Firestorm in DesktopX Themes
by BoXXi

This is a theme that immediately caught my eye. It's hard for me to describe, but that's not a bad thing. You just need to download this and check it out.

Download





Electric Twist in Dreams
by TheMasterBaron

This Dream can be a little busy for some, but overall it's a nice creation of colors and looks pretty cool on the desktop.

Download





The land of sky blue waters in Wallpapers
by teddybearcholla

I really like the watercolor look of this wallpaper. Always nice to see something different and subtle. Very nice work.

Download





Easter Eggs in Wallpapers
by sydneysiders

Well Easter is approaching, so this obviously fits right in. It's a real nice Easter Egg wallpaper, so be sure to hop (get it...hop) on over and check it out.

Download





W1 for WindowBlinds
by windoe

A real nice dark skin with a nice combination of colors. Be sure to check out his personal page on WinCustomize for more great works.

Download



As usual another great week for submissions. For those who celebrate Easter, have a great holiday weekend and I will see you next week!

WindowBlinds: Change the Color of Your Visual Style

WindowBlinds Custom Color Support

Thursday, April 5, 2007 by Island Dog | Discussion: WindowBlinds

One of the coolest features of WindowBlinds is the ability to change the color of your visual style on the fly.  This is a feature I feel is overlooked sometimes, so I wanted to write a brief guide about it.  It's very simple to use and depending on the skin itself, you can drastically change it's appearance, or just make a slight color change to match a wallpaper. 

Open up the WindowBlinds configuration window and select "Change Colors in Skin", then check "Enable custom color support".  The sliders will now become active and you are free to adjust them to obtain the color you want.  The preview window will give you a real-time view of what color changes are being made. 


You also have the options for HSL based coloring, and Gamma adjustment for even more control.  Once you find the color that fits just hit "Apply my changes" and your new color will take effect.  To undo the coloring just uncheck the "enable custom color" box, and hit apply again.

This is my desktop using the OpusOS skin.


This is the same skin with the colors adjusted.


You see with just a few clicks and some slight slider adjustments you can alter a visual style to your liking.  It's also great for skins that you might have used often, and would like to "update" them with a new look. 

 

Learning DX Step-By-Step - #5

Using WMI

Thursday, April 5, 2007 by RomanDA | Discussion: DesktopX Tutorials

Step-by-Step Tutorials

#5 - Using WMI

A series by RomanDA

Listing of other DX Tutorials: Click here
Today's Lesson: "Using WMI" Windows Management Instrumentation

In this lesson we will cover how to use Microsoft's WMI to find out some basic info about our windows computer.
In order to use these Tutorials you will need to purchase DesktopX for $14.95 from Stardock.
Lets get started.

STEP 1 - Create a text object.


I'm not going to go back over the first 4 tutorials, if you haven't read them, and gone thru them, please go back and do that first.

Create a TEXT objet, make the default text something like "TEST" it doesn't matter, make it the size you want (big enough to read on your screen).

 

We are simply going to be using this text object to display the info we gather.  Again, this is just to show you HOW to use WMI to retrieve info from your computer, not how to make a pretty widget.  We can do that later. 

 

Don't worry about adding scripts yet, we will do that in a later step.

STEP 2 - WMI Basic connection


WMI is used to pull information from your system, things like Computer name, User name, What drives are attached to your system.  We are going to pull this information from your computer using a simple script in DX.

Open your object, click on NEW for the script.
We will be adding some info to the "Sub Object_OnScriptEnter"
 

Vbscript  Code
  Dim objWMIService
Set objWMIService = GetObject("winmgmts:\\.\root\cimv2")
Set compinfo = objWMIService.ExecQuery ("Select * from Win32_ComputerSystem")
 
The DIM is used to Declare variables and allocates storage space.
The first SET command is used to make the connection to the local computer.  I could get all technical on this part, but if you really want to know all the details on this connect string visit this site.
The 2nd SET command is used to pull the information you want from the computer.  In this example we are wanting to get the user name, domain name, and computer name.  This works like a SQL Query string, there are a ton of options for this as well.  Again, this is a BASIC tutorial, so if you want more details, look the commands up.

Lets break this line apart:
Set CompInfo Set the variable CompInfo to the info we pull from WMI
objWMIService objWMIService was setup in the previous SET command to
point to the WMI service.
.ExecQuery ( Execute a query into the WMI database
"Select * we want to "SELECT" * - EVERYTHING
we could have picked just 1 item if we only wanted say the Username, etc.
from Win32_ComputerSystem") The data we want is coming from the Win32_ComputerSystem part of WMI
There are DOZENS of these tables in WMI.

HERE is a great place to learn all about WMI
 Lets look at what information we can pull from this one table:
I'm not going to go through ALL of this, I just want you to see what is available from this 1 table.
 
WMI Information
  class Win32_ComputerSystem : CIM_UnitaryComputerSystem
{
  uint16 AdminPasswordStatus;
  boolean AutomaticManagedPagefile;
  boolean AutomaticResetBootOption;
  boolean AutomaticResetCapability;
  uint16 BootOptionOnLimit;
  uint16 BootOptionOnWatchDog;
  boolean BootROMSupported;
  string BootupState;
  string Caption;
  uint16 ChassisBootupState;
  string CreationClassName;
   sint16 CurrentTimeZone;
   boolean DaylightInEffect;
   string Description;
   string DNSHostName;
   string Domain;
   uint16 DomainRole;
   boolean EnableDaylightSavingsTime;
   uint16 FrontPanelResetStatus;
   boolean InfraredSupported;
   string InitialLoadInfo;
   datetime InstallDate;
   uint16 KeyboardPasswordStatus;
   string LastLoadInfo;
   string Manufacturer;
   string Model;
   string Name;
   string NameFormat;
   boolean NetworkServerModeEnabled;
   uint32 NumberOfLogicalProcessors;
   uint32 NumberOfProcessors;
   uint8 OEMLogoBitmap[];
   string OEMStringArray[];
   boolean PartOfDomain;
   sint64 PauseAfterReset;
   uint16 PCSystemType;
   uint16 PowerManagementCapabilities[];
   boolean PowerManagementSupported;
   uint16 PowerOnPasswordStatus;
   uint16 PowerState;
   uint16 PowerSupplyState;
   string PrimaryOwnerContact;
   string PrimaryOwnerName;
   uint16 ResetCapability;
   sint16 ResetCount;
   sint16 ResetLimit;
   string Roles[];
   string Status;
   string SupportContactDescription[];
   uint16 SystemStartupDelay;
   string SystemStartupOptions[];
   uint8 SystemStartupSetting;
   string SystemType;
   uint16 ThermalState;
   uint64 TotalPhysicalMemory;
   string UserName;
   uint16 WakeUpType;
   string Workgroup;
  };

What we want from this table is:

  • UserName  - User Name
  • TotalPhysicalMemory - Total Memory
  • Domain - Domain name (If there is one)
  • Name - Computer Name

STEP 3 - Pulling info from WMI


So, we know how to make the connection to WMI, and we know what table we want.
Lets get the USERNAME that is logged into the current computer.
 

Vbscript  Code
  For Each objComputer In CompInfo
  PCName = objComputer.Name
  Next
  object.text = "ComputerName: " & PCName

Let's look over this one too.

I'm not going to break everything apart, but the basics are this:
the FOR EACH is used to pull 1 item at a time from the COMPINFO we set before, and store it in the objComputer variable. 
Then we assigning the variable PCName to the .NAME field from the table.
Then we take and set the TEXT of the object to "ComputerName: " & PCName

SAVE & APPLY this now, and see what happens.
What you SHOULD see is your text object showing something like:
ComputerName: MyPcsName

Not to hard was it?  Lets add a little more.
 

STEP 4 - Adding more info


Open the object back up, EDIT the script.  Lets add a little more info.
 

Vbscript  Code
  For Each objComputer In CompInfo
  PCName = objComputer.Name
  PCDomain = objComputer.Domain
  UserName = objComputer.UserName
Next
  object.text = "ComputerName: " & PCName & vbnewline
  object.text = object.text & "Domain: " & PCDomain & vbnewline
  object.text = object.text & "UserName: " & UserName & vbnewline

We added the Domain name (if there is one, you may not have one), and the Username.
Notice the USERNAME has the domain name as part of it? (if you have a domain, otherwise you wont see this).
We want to pull JUST the user name out from that. So lets add a simple IF statement to the script.

Vbscript  Code
  If len(PCName) > 1 Then
  t = len(PCName)+2
  UserName = mid(UserName,t)
End If

Insert this script right below the UserName = objComputer.UserName line.
This simply looks at the PCName to see if its LENgth is over 1 character
Then it gets the length of that name + 2 spaces (the \ and then the first letter of the name)
Then it sets UserName to the MIDdle of the the string UserName starting at the T postion.

Don't worry I will put the entire script at the bottom in one place, so you can copy/paste it if you want.

STEP 5 - What Drives do we have?


We are going to add a little more to this script.  One of the things people have asked to see is how to determine what drives, drive letters, etc. are on your pc.

 

The code we are going to add looks a lot like what we used above:
 

Vbscript  Code
  Set objWMIService = GetObject("winmgmts:\\.\root\cimv2")
Set DriveInfo = objWMIService.ExecQuery ("Select * from Win32_LogicalDisk")
object.Text = object.Text & vbnewline & "DeviceID | DriveType | Description "
object.Text = object.Text & " | VolumeName | FreeSpace | FileSystem"
For Each objDrive In DriveInfo
  object.Text = object.Text & vbnewline & objDrive.DeviceID & " | "
  object.Text = object.Text & objDrive.DriveType & " | " & objDrive.Description
  object.Text = object.Text & " | " & objDrive.VolumeName & " | "
  object.Text = object.Text & objDrive.FreeSpace & " | " & objDrive.FileSystem
Next

We are pulling a lot of info from the WIN32_LogicalDisk table.  add the code, see what shows up.
You should see something like:

DeviceID | DriveType | Description | VolumeName | FreeSpace | FileSystem
C: | 3 | Local Fixed Disk | Boot-2006b | 30640107520 | NTFS
D: | 3 | Local Fixed Disk | Storage-2006b | 14589018112 | NTFS
E: | 5 | CD-ROM Disc | 20030803_1304 | 0 | CDFS
F: | 5 | CD-ROM Disc | | |

STEP 5 - Here's The code:


Promised to post all the code in one place, here it is:

Vbscript  Code
  'Called when the script is executed
Sub Object_OnScriptEnter
 Dim objWMIService
 Set objWMIService = GetObject("winmgmts:\\.\root\cimv2")
 Set CompInfo = objWMIService.ExecQuery ("Select * from Win32_ComputerSystem")
 For Each objComputer In CompInfo
  PCName = objComputer.Name
  PCDomain = objComputer.Domain
  UserName = objComputer.UserName
  If len(PCName) > 1 Then
   t = len(PCName)+2
   UserName = mid(UserName,t)
  End If
 Next
 object.text = "ComputerName: " & PCName & vbnewline
 object.text = object.text & "Domain: " & PCDomain & vbnewline
 object.text = object.text & "UserName: " & UserName & vbnewline

 Set objWMIService = GetObject("winmgmts:\\.\root\cimv2")
 Set DriveInfo = objWMIService.ExecQuery ("Select * from Win32_LogicalDisk")
 object.Text = object.Text & vbnewline & "DeviceID | DriveType | Description "
 object.Text = object.Text & " | VolumeName | FreeSpace | FileSystem"
 For Each objDrive In DriveInfo
  object.Text = object.Text & vbnewline & objDrive.DeviceID & " | "
  object.Text = object.Text & objDrive.DriveType & " | " & objDrive.Description
  object.Text = object.Text & " | " & objDrive.VolumeName & " | "
  object.Text = object.Text & objDrive.FreeSpace & " | " & objDrive.FileSystem
 Next
End Sub

CONCLUSION


There are a lot of things that can be done with this info.  Things like making a Drive monitor, or a simple piece of text with your username etc on it.
WMI is EXTREMELY powerful, you can pull things from other computers on your network, A simple GOOGLE search will show you TONS of places with lots of script examples. 

Check back as I add new Step-By-Step Tutorials on how to make this a link to a folder, web-site, or just about anything you want!

I hope you have enjoyed this step into DX, and look forward to the next installment.

Enjoy,
RomanDA
http://romanda.wincustomize.com

IconPackager 3.2 supports Windows Vista

Change your icons on Windows XP or Windows Vista

Wednesday, April 4, 2007 by Frogboy | Discussion: IconPackager Talk

IconPackager is a program that allows users to change all (or nearly all) the icons in Windows by applying "packages" of icons.  Way back long ago, it was the very first program designed to do this on Windows. 

Over the years, the demands of icon artists have grown.  When IconPackager was first released in early 1999, icons came in two basic sizes -- 32x32 with 16 colors and 16x16 with 16 colors.  With the release of Windows Vista, icons support 256x256 true color, alpha blended icons down to 16x16 and everything in between.  Consider how large 256x256 is -- that's about the resolution of a DOS game 10 years ago.

IconPackager has continued to evolve.  The IconPackager format remains the defacto standard for distributing sets of icons to be used to change all the icons at once on a Windows system.  With IconPackager 3.2, Windows Vista's new icon features gain explicit support.

Giving Windows Vista a new iconic look

Windows Vista has lots of icons. And many of those icons are quickly seen by users.  For instance, the User Folder is a new folder in Windows Vista that users are likely to see.


User Folder in Windows Vista

In Windows XP, users noticed desktop icons and the Start menu icons.  In Windows Vista, the Start menu has fewer icons but there are a lot more icons elsewhere such as the new user folder.

The Challenges of Windows Vista

Of all the OSes IconPackager has supported, Windows Vista has proven the hardest to tame so far.  That's because Microsoft seemingly went out of their way to make Vista less friendly to icon changing.  Besides there being more icons to change, Windows Vista actually only uses 4 sizes of icons -- 256x256 (which is a new size), 48x48, 32x32, and 16x16.  When sizing icons, if a 256x256 icon isn't  available, it will use the 48x48 icon -- even if a 128x128 icon is available.

Moreover, Windows Vista will not scale up icons. It only scales down.  That means that if a 256x256 icon isn't available and you want to have your icons be say 128x128 in size, too bad, it'll just use the 48x48 and keep it in a tile:


Classic icon packages like Copperdeck won't size above 48x48 even though larger sized icons exist within the icon resource

For IconPackager 3.2, Stardock went ahead and refreshed the new included icon packages to support 256x256 (and unfortunately, Stardock IconDeveloper doesn't yet support Vista 256x256 icons).  But we are hoping to add support to on-the fly up-conversion so that icons which have at least 128x128 icons in them will be scaled to 256x256. A 2 to 1 ratio results in almost no difference in quality and would allow most of the popular icon packages to be used on Windows Vista without needing to be updated.

Folders on Windows Vista

The other challenge on Windows Vista are folder icons.  Historically, icon artists would simply create a generic folder and IconPackager would then replace the Windows default folder icon with the one created by the icon artist.

But on Windows Vista, it's a whole new world. Windows Vista has "live" folder icons. The folders on Vista show little thumbnails of what's inside. Cool eh?


Oh isn't that cool? The folder opens up and shows what's inside! Great right? Right???

 

But how do you change that? Well, it turns out you can if you look at that folder icon as two icons -- the foreground and the background. Of course, under the covers, it's a lot more complicated than that of course but to make folder icon changing accessible to icon authors, we were able to break it down into two images for the folder that the icon artist would have to make.


Changing the folder icons on Windows Vista involves a little more work -- the default folder icon is broken into two images.

 

An updated look

Since Windows Vista looks prettier, we figured it was time to update the look of IconPackager.  As much as we know people enjoyed the Windows NT 4.0 look and feel of IconPackager, we decided to update it with a new look.

Not just good for Windows Vista users

Windows XP users gain from the various tweaks we've made. They're relatively minor (at this stage, we have changing icons on Windows XP pretty nailed down).  But still, any change at this stage on XP is still good.

And for Windows Vista users, as good as the Windows Vista icons look, now you can personalize them to your own preference.


There are thousands of icon packages available and now Windows Vista users have options

Vitals

IconPackager is a free download from Stardock.  You can purchase it on its own or purchase it as part of Object Desktop which includes not just IconPackager but WindowBlinds, DesktopX, RightClick, Theme Manager, etc.

Visit: IconPackager home page




web-wc01