![]() Use window blinds xp to add themes.find themes, widgets, and other. But no cash.Windowblinds xp 133 windows themes.windowblinds is a computer program that allows users to skin the windows.windowblinds 3 accompanied the release of windows xp.windowblinds multi.windows makes organizing windows.visual styles vote wallpapers winamp windowblinds windowblinds xp windows styles.apply skins to your windows, applications.stardock corporation. I definitely would not mind having WB on my machine. Cant this info be stored in msstyles ? WB skins do support this. I am no skinner, but I have noticed that msstlyes skin do not change the tooltip. Most of the skinners here would like to use something that is free for all which I beleive is the reason for the skins that we see for msstyles. Admittedly there are no chaninjas there but some of the work is top notch. Does the reg version take less?Īnd I do not think that there are no good themes for WB. So is that not enough for WB and msstyles. That said I beleive a lot of peopl who do skin their machines have at least 256MB RAM. So if I am running WB that means that I am running WB+mstheme. Am I right in assuming that WB requires the MS theme engine to be running. I have a small doubt on the resource usage of windowsblinds. And I think that's a pretty valid argument. msstyles so at that point, it would be hard to argue that msstyles is superior.īy then I think it'll be a "uxtheme.dll patch is free, WindowBlinds is $20". For instance, WB can skin the mouse over highlight area on your XP start menu (on an msstyle you get a colored block, on WB it can be skinned which can look quite nice).īy WindowBlinds 4, UIS will be a complete superset of. On the other hand, WB keeps adding nice things to XP that become quite noticeable in a hurry. But it doesn't do shellstyles yet (WB 4 will) - shellstyles are the task panes on the left side of your folders. It has vastly more features and flexibility. WindowBlinds is a superset (for the most part) of msstyles. msstyles vs.uis then things get more complex. WindowBlinds 2.x will work on Windows XP service pack 1 (as well as WB 3 and in fact I've heard that WindowBlinds 1.x even works). There is also the advantage that you don't have to repatch or anything when a new version of Windows XP arrives. And remember, even with all these features, it uses less memory than a visual style does because of years of optimizing for memory (admittedly, if we were writing just for XP WB wouldn't be so tight but WindowBlinds has to work on Windows 98 too and thta means every kilobyte counts). ![]() I can even make my skins become grayscale, modify the gamma on them and even invert the colors entirely which is pretty neat. You just need one and can colorize it as you want. There is also the advantage that WindowBlinds can colorize skins on the fly. And Stardock has the support of both Microsoft and the hardware companies who can specifically accelerate the functions visual styles need (which will help msstyles too but it'll help WB more since we use their drivers more). And WindowBlinds 4 is already in internal alpha which is even more feature rich, uses even less memory, and is even faster. Compare WindowBlinds 3.0 from last year to WindowBlinds 3.41 and even there you have a big difference. I'm a biased source (I work for Stardock) but there is one big advantage engine-wise - WindowBlinds continues to move forward on a monthly basis. A person who sends to have the same programs up all day will find WB faster. A person who is constantly loading and unloading programs may find WB slightly slower. That's why you see these debates sometimes. But WindowBlinds skins are slower at loading into a new process than msstyles. WindowBlinds is faster at drawing than XP because WindowBlinds visual styles are hardware accelerated. WindowBlinds on XP thus inherits that.īut there are other APIs in XP that haven't been tapped into yet. Microsoft ran into the same problem (obviously) so on XP they changed the windowing code to not have that issue. That's why people on those OSes would run into problems of windows shrinking when reloaded or moving or whatever. For instance, WindowBlinds on 2000, 98, and ME had to use a "fake titlebar" to do its thing. That said, Microsoft added a host of new API calls into Windows XP to use on their engine. The XP visual style engine is based off of WindowBlinds so saying it's more "native" isn't justifiable. Are you talking formats or are you talking engines?Įngine wise, they are basically identical.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |