Brad Wardell's Blog

Fun with WindowBlinds 6 colors

Published on Saturday, October 6, 2007 By Brad Wardell In WindowBlinds

Making your own color presets

One of the coolest new features of WindowBlinds 6 is the ability to selectively color parts of a skin. Combined this with another new WindowBlinds 6 feature - user created substyles and you have customization heaven.

For this demo, I'm going to show off a skin that hasn't been released at the time of this writing - Turbo.  Turbo is a new skin from Stardock Design that is being released exclusively for Object Desktop users.  It's not quite done yet - you will see some minor graphical glitches in the screenshots - but it will serve our purposes of what you can do with selective coloring.

First, let's look at Internet Explorer 7 on Windows Vista by default:

For a skin to be relevant, it has to look as good or better than the original. Aero looks pretty good I think but has some minor UI issues that are a matter of taste (I don't like that the address bar looks like it is part of the title bar, it might be a matter of taste but I think it harms the UI context).

Here is Turbo running Internet Explorer 7:

Turbo has a graphical glitch with the address line still but the site address and search field are clearly part of the client instead of part of the title bar. The status bar is also a lot cleaner.

But the important part and why I chose Turbo for this demo is that the skin has 3 main colors - black, red, and yellow.  In WindowBlinds 5, you could hue shift the whole skin but the results wouldn't have been desirable. In WindowBlinds 6, things are different.

Step 1: Create a substyle

WindowBlinds has supported sub-styles for a long time.  But with WindowBlinds 6, users can create their own mini sub-styles called presets that allow them to customize a particular skin and then save it as a sub-style.  So here we're going to do just that.  ON the Colours tab, create a new sub-style.


Create a new preset.


Give your preset a name.

Step 2: Turn on colorizing.

Once you've made a new preset, select the option to colorize your skin (see left side).  There is a small button in the middle that activates the selective coloring option. Once clicked, you get the advanced HSL colouring dialog.


Turn on coloring, then opt to use the selective colouring mode.

Step 3: Choose the color you want change

This can be a little tricky when you first start. The easiest way is to grab the little color picker on the right side and drag it (holding down the mouse button) onto the color you want to change.


Drag the color picker to the part of the skin whose color you want to change

The two sliders you see on the right determine which color you want to change. The second slider determines the color range -- how many similar colors do you want to include in your color changing?

And that's it.

Here are some example of it in action:

Note how the red buttons remain red. And there are areas that use other colors as well such as push buttons that have green mouseovers. In this way, users have a lot more control over the look of their skin and one skin becomes many.

For more information on WindowBlinds 6, visit www.windowblinds.net. 

Why don't liberals start more charities?

Published on Saturday, October 6, 2007 By Brad Wardell In Democrat

The far left in the United States are outraged that Bush vetoed the bill that would have provided "free" health insurance to minors.

When these discussions get going, I am always amazed that the obvious solution isn't taken: Start charities that provide health insurance to the "needy".

It wouldn't be that hard to do.  Those who really feel strongly about paying for health insurance for other people could donate to these charities. Then, those who wanted said health insurance would send in their past year's tax return along with proof of children and then be given health insurance for that child. 

These kinds of charities already exist for people who have a random illness like cancer, breast cancer, childhood diseases, etc.  So what is the difference?  The difference from my limited research is that most of these charities and their fund raising are performed by conservatives (particularly religious conservatives). 

As was documented in the excellent book "Who really cares" American liberals have replaced concrete action with political belief.  To them, posting a blog or protesting or some other symbolic but ultimately futile gesture is the same as actually doing something.

For this reason, American liberals are much more inclined to support federal government provided projects for the needy because it takes the burden of having to do anything to back up their political beliefs.  The sacrifice and effort is transferred to other people (typically people who disagree with their views and are hence demonized by the left even as those they demonized are, as a practical matter, the ones actually doing the doing).

It is a pity conservatives aren't more inclined to step up and ask "Why not start a charity?" when an advocate of a socialist policy starts railing for some new government welfare program.  After all, the left routinely says "Why don't you volunteer for the military?" when a conservative supports US foreign policy.

Galactic Civilizations II: Twilight of the Arnor

Published on Friday, October 5, 2007 By Brad Wardell In GalCiv II News

BETA SCHEDULE

The second expansion pack to Galactic Civilizations II is about to go into beta. For Galactic Civilizations II: Twilight of the Arnor, we're going to try something different. Something that we think will be particularly fun.

The biggest single feature of the expansion pack isn't the Terror Stars, which are admittedly pretty cool. And it's not the map editor, campaign editor or scenario editor which do add a lot of new possibilities. And it's not even the Metaverse tournaments, which will probably be pretty popular. Nor is it the updated graphics which do bring Galactic Civilizations II up to a whole new level. No, it's the unique technology trees per player.

Let me emphasize this: The fact that each of the 12 major races will have their own technology trees we think is a major milestone for this type of game. The implications of it are far-reaching since technology trees are from whence ship components, planetary improvements, etc. come from.

Let me further add that these technology trees are not just cosmetic changes. Let me give you a couple of examples: The Arceans don't get Warp Drive or any other higher level propulsion techs. Instead, they have special factories unique to them that allow them to make their own ships faster. The Yor don't have factories but instead have collectives that produce based on their population. And, did we mention...these techs are tradeable back and forth. But thanks to a new AI enhancement (a willingness to trade a particular tech variable) tech trading will become vastly more intelligent.

So for the beta, to reward the users who are pre-ordering the beta (and hence funding this project) we are doing something special: The betas will introduce the unique technology trees in small groups so that players can really see the impact of them and have a chance at being introduced to them and be able to make suggestions on how they can be tweaked.

Below is the tentative schedule: UPDATED

  • Beta 1: October 25th - Terran Alliance, Drengin, Arcean technology trees

  • Beta 2: November 8 - Yor, Torian, Korath technology trees added

  • Beta 3: November 20 - Korx, Drath, Iconians trees added

  • Beta 4: November 29 - Thalan, Altarian, Krynn technology trees added

  • Release Date: December 12.

As much as we've enjoyed Dark Avatar as an expansion pack, I am certain that Twilight of the Arnor will be liked even more by players.

To pre-order Galactic Civilizations II: Twilight of the Arnor visit here.

Two developers discuss problems in Vista

Published on Thursday, October 4, 2007 By Brad Wardell In Windows Vista

I like Windows Vista quite a bit. I like it a lot more than Windows XP.  That said, it's not perfect. There's been a real dog piling on this but me and the Greenreaper had an interesting conversation on 10 issues in Windows Vista that could be rectified.

Problem #1: The UAC. The most obvious new "security" feature in Windows Vista is the User Access Console known as the UAC. Type in "UAC sucks" into Google and you'll get tens of thousands of results. No single feature in Windows Vista has done more to harm the first impression of Windows Vista.  But it could have been avoided.

The UAC is a prompt that comes up whenever the user does something that requires elevated "priviledges" to run. This can include everything from installing software, changing your screen resolution, to any number of seemingly trivial things. Even if you are logged on as an administrator, you will see this prompt..often.

The implementation of the UAC is unbelievably bad.  There are no fewer than 4 different dialogs (each looks different) that can come up depending on the circumstance. 

The net result is that many users have simply disabled the UAC which undermines much of Windows Vista's new security initiatives.

Solution: The UAC concept isn't bad, it's the implementation.

  1. First off, Microsoft needs to have the UAC prompts be consistent.
  2. The UAC shouldn't change the screen resolution (there's a security reason they do this but Microsoft needs to have this be an option as it's extremely annoying). This option should not be hidden in group policies but somewhere easy to find.
  3. The UAC should remember what programs and settings the user has given permission to and have an option to "Always Permit" that application or setting to be elevated.
Greenreaper responds:

Reading what you said about the "circumstances" for UAC, I would have been unclear about what you meant, unless I already knew about it. I think it could use more explanation.

 

As for why they had the differences, my understanding was that they were intended to indicate differing levels of likelihood of danger - for example, a Microsoft signed app is viewed as less dangerous than a generally signed app, which is viewed as less dangerous than a random executable. There are ways around it but most virus/malware writers are *not* that smart, and it seems reasonable for there to be some differentiation - you don't want to be as seriously worried when you're launching control panel as when you launch a random executable from the Inernet.

 

That said it would indeed have helped to have more options for customizing it, though I suspect the "always permit" option would be used a lot more often than Microsoft would like.

Problem #2: Releasing Windows Vista before the drivers were ready.

As a practical matter, the first beta of Longhorn that was remotely useable was late Summer of 2006 -- just 6 months before release.  That gave everyone only a matter of months to get their software (and drivers) ready for Windows Vista.

This has been particularly problematic with video drivers. Many early adopters have discovered that their favorite games and other applications have problems with the video drivers.

The rush to get Windows Vista out by the end of 2006 resulted in an OS whose video drivers just weren't ready for prime time and this has had significant consequences in user perception of performance and compatibility.

Solution: Make sure Service Pack 1 doesn't ship until the second-generation video drivers are ready and bundle them in.

Greenreaper responds:

Yes. Microsoft underestimated how long it would take the driver manufacturers to adapt to a major new driver model. Perhaps they really thought people would drop everything else they were doing and concentrate on LDDM when it first came out. Most likely the driver teams were being driven internally to create XP drivers for linking two graphics cards together at the same time, and decided it wasn't really worth looking at until it solidified.

Other driver teams were also affected due to x64 driver and signing requirements, though this was partly their own fault for not doing it earlier.

Problem #3: Eliminating GDI hardware acceleration.

Windows Vista has a new desktop window manager (the DWM) which provides 3D acceleration to the desktop. This is very nice for future applications.  But in the process of doing this, Microsoft eliminated 2D acceleration entirely.

For the past decade, Windows programs have used GDI for their on-screen drawing. And video card manufacturers provided hardware acceleration for this.  But now in Vista, this acceleration is gone and the result has been a noticeably slower desktop -- particularly with programs that make heavy use of GDI drawing routines.

It's a little flabbergasting to developers who were told to use GDI and GDI+ for years to suddenly have their apps no longer performing as well as they did on Windows XP. I am not even sure why Microsoft did this.

Solution: Bring back GDI acceleration

Greenreaper responds:

I think Microsoft's official view is that we care about performance we should just be using DirectX, or WPF, both of which are hardware accelerated. Obviously this is not entirely practical in some (a lot of) situations, in part because it does not have a good system of fallbacks in the lack of hardware support for a particular operation, but also because we have to work with everyone else. DX 10 solves the first problem because just about everything *has* to be supported - but then you can only develop for Vista, so you might as well use WPF anyway and rely on its fallbacks . . .

 

if you can find the tools and samples you need, and if it's even an option for you (obviously WindowBlinds could find it hard to work well using WPF).

Problem #4: UI changes for the sake of change

At work, my laptop's wired IP address is assigned by the DHCP server. At home, I have it hard-coded to a specific IP.  Not only has Windows Vista not made it easier to have multiple configurations for network adapters, they have made it much more difficult to go and change the existing settings.

In Windows XP, from the Start-menu if one wants to change their IP address they could go to "My Network Places" and then click on "View Network Connections".  On Windows Vista, getting to the same place requires additional steps.  Changing something as basic as your IP settings should be easy.

Solution: Let people create different network configurations that they can easily switch.

Greenreaper responds:

Things are certainly confuisng in some areas. It took a fair amount of time for me to get rid of all the duplicate wireless network settings I had built up over time, I had a hard time even finding the list and when I got there I saw over ten networks. When I got rid of all the duplicates, I found I could actually connect to Kris' network automatically again, when I hadn't been able to for a long time. An example of bad usability actually causing a feature to break.

Problem #5: The new Start Menu

I really like the search being built into the Start menu. It's very handy to be able to type a word in and have it quickly find the program.

On the other hand, losing the fly-out menus to a cramped listbox for showing programs is ridiculous.  How did this bad UI get into the final product?

Solution: Provide an option for fly-out menus.

Greenreaper responds:

Nothing to disagree with here, but I would note that the Classic start menu is surprisingly usable. Saves over 1Mb in memory and 40/30/60 kernel handles/USER objects/GDI objects as well. Of course, the XP one probably isn't much better. Still, I think Classic works better as a menu - and isn't that the point of the Start menu?

Problem #6: Unbelievably bad desktop operation performance.

Whether it's unzipping a file or copying a few files around, Windows Vista is incredibly slow now.  How did this happen? Windows Vista now insists on estimating how long it will take to copy files -- and the estimation process is usually longer than it would take to copy the files.

If I unzip 200 files from a command prompt, I can do it in a second.  If I do it with the built in Windows ZIP, it can take several minutes.  Next time you see someone on a forum say "I wish Microsoft would bundle in some feature" remember how crappy the ZIP handling got (but still "good enough" to take the low hanging fruit from ZIP utility vendors).

Copying files from the GUI is similarly slow. It's should be much much faster. Again, if you use a third party file manager or a command prompt it's very fast.

Solution: Fix the ZIP support and copying. Get rid of the "estimating time" portion (use those "thead" things and do it in the background_.

 

Greenreaper responds:
There's been a lot of speculation for the causes of this, from poor network handling to the kernel not releasing buffers soon enough to having to update the Explorer treeview and wait until it's completed. I think it's one of those "didn't have enough time to bring everything together and polish it, just enough time to make it work at all" situations.

Problem #7: Upgrade Pricing is far too high

I have a lot of PCs running Windows XP Professional. I'm the only person who uses these machine. I've got my gaming rig. My test box rig. My power laptop. My tiny laptop.  Now, Microsoft would say (correctly) that I represent a tiny fraction of the user base. But I do represent a pretty large % of the early adopter profile -- the people Microsoft should be trying to migrate to Windows Vista as quickly as possible.

And yet, even if I use the Windows Vista "Family Discount" where I paid $259 for the "Upgrade from XP" for Windows Vista Ultimate, I still pay $50 apiece for 2 additional licenses.  So to get me and 3 machines to Windows Vista, I am paying $360.  That's more than a new Xbox 360 system!

Does Microsoft really think there's that much new value over Windows XP in Vista? Really?

Solution: Family Discount should be $30 and be up to 3 licenses. The Upgrade Pricing should be 50% less than it currently is. (Vista Home Premium Upgrade is $160 right now. What is in Windows Vista that is worth $160?).

Greenreaper responds:

Does Microsoft really want people upgrading at all? I'd have thought it's almost more profitable for them to have the users buy it on a new computer.

 

They're less likely to have problems (both performance and general

technical) and if they do the're less likely to complain directly to Microsoft about them. Perhaps the upgrade pricing is a buffer against this.

 

Everyone wins in terms of efficiency if you buy it with a new PC, though it does mean you have to shell out for a new PC.

 

Problem #8: Microsoft Marketing failed to make compelling case for Windows Vista

This really ties into #7.  Microsoft believes that Windows Vista Home Premium Edition is worth $160 for users who already have Windows XP.  Okay, it's marketing's job to make that case.  What's in Windows Vista Home Premium that adds up to $160?

If you go to www.windowsvista.com you see these bullet points:

  • Flip3D (I can do much of this stuff with WindowFX on Windows XP). But let's say the new Aero stuff is worth $20 -- which is how much a third party would charge for it.
  • Desktop Search. Okay, but Google gives this away for free.  
  • Windows Sidebar. You can get Google Gadgets, Yahoo Widgets, or Stardock DesktopX for free or very cheap.
  • Windows Photo Gallery. Okay, this is nice but I mean, is it really that big of a deal?
  • Windows Defender. This is free for Windows XP users.
  • Media Center.  Okay, the new Media Center is very well done.  I can get Beyond TV 4 for $70. It's not as good but then again, they're not selling 100 million units a year.
  • DVD Maker. Is there anyone with a DVD player that didn't get a DVD making utility?
  • Niche goodies. There are some neat things in Vista like Windows Meeting Space but they're not the kinds of things that you could use to sell Vista.
  • Misc. Minor features are listed like Super-Fetch, Self-Healing, Diagnostics,

Now, perhaps I'm way off here but I jut don't see $160 of new stuff. Especially for the increasing number of people who have multiple licenses of Windows XP. Heck, even the crummy Home Basic is $100 and that doesn't even have Aero or the Media Center.

Don't get me wrong, I like Windows Vista.  I just don't think it was a good idea to have it priced this high unless Microsoft was prepared to make a better case on the marketing side. 

Solution: Microsoft did a very good job with the Windows Featured Community project. One wonders how things might have gone if Microsoft didn't have dozens of high-profile tech sites feeding users the new features of Windows Vista.  But there is more that needs to be done.  Microsoft needs to get its evangelists out there more.  It needs to promote WindowsVistaBlog.com more and make it easier to get that info out there.

Greenreaper responds:

I'm one of the people who might be willing to upgrade for the promise of increased general performance. The kernel team has not spent 6 years doing nothing, so there must be some value in there. For me, it's not so much having the latest and greatest *features* so much as having generally better performance. Consider it similar to a Linux kernel upgrade. Unfortunately, this is crippled by the poor performance of the shell and a generally increased memory footprint. It does no good for disk operations to be 20% faster if there are 50% more of them.

Problem #9: The Development Tools were not ready for prime time

If Windows Vista launched and there were a bunch of compelling programs available for it on release day, then that $160 upgrade price might have been more compelling. 

Unfortunately, writing Vista specific stuff has been no panacea. Getting your Visual Studio 2005 up to writing Windows Presentation Foundation apps is an arduous process. And even when you do, the available documentation and inconsistent performance (see video driver part) mean that many cool stuff that Windows Vista makes possible isn't really practical yet.

Solution: Update Visual Studio soon to have all the "stuff" on a single DVD with a more seamless installation process.

Greenreaper responds:
Agreed, and yes, it wasn't just the technical tools. It's never easy keeping up with a new operating system. However, this has been a death march for external developers as well as internal ones. Never before has there been so much gunk to plough through in terms of new APIs and application frameworks (some of which are later discarded), only to find that important things still haven't been documented; most likely because they were just added this build. Perhaps I just don't have enough experience with OS releases - I suspect the documentation issue is true in most cases - but it seems to have been drawn out to an exceptional extent. How many millions of dolllars does Microsoft make, and it still couldn't get this right?

Problem #10: Stupid Icon Handling

The good news is that Windows Vista has much nicer icons. The bad news is that Windows Vista's icon implementation is awful.

Here's the deal: If you don't have a 256x256 version of an icon, the icon displayed is the 32x32 or 48x48 one.  Even if you have a 128x128 icon (which many icons have) it will still use the 32x32 or 48x48 one. 

So even if your icons on your desktop are sized at 128x128 and the icons in question have a 128x128 version, it won't use that version but will instead look to see if there's a 256x256 (and shrink it down) and failing that just show the 48x48 or 32x32 version which looks ridiculous.

Solution: Support the Windows XP icon format better -- if there's a icon that's the right size then use it.  Don't abandon all those high resolution icons.

Greenreaper responds:

Agree totally, there's no real excuse for this - even if an icon is not in the right format to start with, there are things that could be done, but they didn't do it. Perhaps a ploy to get people to make more Vista icons?

 

It'll just backfire; most people are going to be too busy or too lazy to recreate icons, even if they have the ability to do so. It might have helped if they'd made a proper tool for making them (though I'm sure the creators of third-party icon editors would complain).

Conclusions

So that's a conversation between two techies on these 10 issues regarding Windows Vista.

WindowBlinds 6 is released!

Published on Tuesday, October 2, 2007 By Brad Wardell In GalCiv II News

 If you like how Stardock develops its games, one of the big reasons it is able to do that is because of the other side of Stardock's business: Desktop experience software.

Programs like WindowBlinds and its big-brother suite, Object Desktop provide the capital through their sales which enables Stardock to develop its games without requiring any outside capital which enables it to make the games how it wants and release them when it wants.

If you don't have WindowBlinds, now's a great time to get it. Today, Stardock released WindowBlinds 6.0. It allows users to completely customize the look & feel of Windows Vista.

Screenshots:

    

Review: CNET.com

Download: http://www.windowblinds.net

WindowBlinds 6 specific skins

Published on Tuesday, October 2, 2007 By Brad Wardell In WinCustomize News

Skins (aka visual styles) designed specifically for WindowBlinds 6 are displayed with a special WindowBlinds 6 icon in the gallery. When a skinner submits a skni, they can now choose 2 new options: Optimized for WindowBlinds 6 and Supports Windows Vista. 

As an example, the first WindowBlinds 6 skin from Stardock Design has been uploaded into the gallery and can be found here.

Enjoy!

739 pages 341 342 343 344 345 346 347 348 349 350 Next