WindowBlinds road map

..Where we are now...

In November Stardock released WindowBlinds 3. Its primary goal was to add some additional productivity features over v2, increase compatibility and integrate it more closely into WIndows, particular on Windows XP.

With nearly a million downloads of it since late November and good reviews, we have had to decide what course to go towards next.

On the one hand, there is more to do still on Windows XP. Specifically WindowBlinds 3.0 doesn't handle the IE scrollbars (neither does XP itself but IE6 was modified to be a partially skinnable browser in itself) and it doesn't handle the web window on the left side. And there are a few GUI controls it doesn't handle.

On the other hand, only a small percentage of the public has XP and most *customer* feedback has focused on things like increased performance, more productivity features, greater control over existing skins.

So in WindowBlinds 3.1, coming out in about a week, we've added real-time gamma correction (change the brightness of a skin on the fly as a user), a brand new skinning language known as UIS1 that creates super fast skins (around twice as fast as an XP visual style as well as a roughly twice as fats as a typical existing WindowBlinds skin).

And we got the Smartbutton stuff fixed up. That along with countless bug fixes that affected everyone from Windows 98 users to Windows XP (very hard to support all these different versions of Windows).

We have gotten the web panel stuff skinned but we have to document a format and provide an example skin before we can put that out, that will probably show up in 3.2. The IE scrollbars we just have to futz with to see what it's looking for. Adding more controls (logoff buttons, spinners, etc.) is mainly a matter of just adding it to the skin language and documenting it so we'll hopefully have that in 3.2 or 3.3.

We also want to try to find a way, if possible, to cache skins. For people who aren't paranoid about using up a couple megs of RAM for increased performance, this option would have the skin stored in a central RAM location and new processes would read from that rather than from disk (if successful, there would be no hit over using no skin at all in loading up a program).

There are always, of course, numerous compatibility things we're working on as well. Contrary to what some people not that familiar with Windows XP may think, XP actually has a massive exclusion list built into the registry. Our goal has always been to try to find ways to make WB work on those programs when possible. We'll continue to work towards that as well.

If you have any suggestions or features that you would like to see in the near term, let us know.
4,643 views 13 replies
Reply #1 Top
What about some transparent menus and dialogs like MacOs X ?
And please, skinnable logoff and turn of buttons.

(I am always wondering why when we use a skin, other than the ones from Microsoft, those buttons are transforming to those very ugly ones).
Reply #2 Top
WindowFX handles transparent stuff and shadows.

Yea, I agree with you on the logoff buttons. It' pretty high on the list.
Reply #3 Top
Brad, as we spoke some days ago, WIndowblinds should authomaticly install custom fonts, when they are especified in the UIS and included in the zip file.
Reply #4 Top
This is very good idea Renato!
Reply #6 Top
Yes...if you can get LiteSTEP to load a relevant Windowblinds skin on a theme-change, then surely getting an auto-install of a needed font has got to be a 'Good Thing'[tm]...
Reply #7 Top
Frogboy - We also want to try to find a way, if possible, to cache skins.


/me *drool*
of course i hopefully will have upgraded by the time this is done, but still, got to love the idea!
Reply #8 Top
Support for .png or .tga?

/Griffin Dreams of being able to anti-aliase curves again.
Reply #9 Top
i think to a degree what is needed is just some tidying up of the interface.

for example the new drag target to get program name for setting excluded applications is a significant usability gain.

one of the things i am still waiting for is the reapearance of the main, sortable, list of skins to select the desired one from.

remember all the excitement in the newsgroups when it was anounced the new look WB 2 was going to use for skin selection? it seems wrong to loose this easy and above all fast way of picking a skin to apply.

it is still there for per-application skins. now if only it was as easily available for main skin selection.
Reply #10 Top
Griffinme - Support for .png or .tga?

from the news artical about the release of the new version of skin studio:

* It is now much easier to alpha blend parts of the GUI. WindowBlinds 3.1, for instance, supports TARGA (.tga) files with an alpha channel.
Reply #11 Top
WBConfig exists in the enhanced version of WindowBlinds. You don't need the appearance dialog at all to use that. I use WBConfig 3.0 to deal with skins.
Reply #12 Top
DOH!
i didnt realise that this had already shiped
i will have a look when i get home. bit of a mute point at work given this machine will only run WB 2.21b
thanks for that
Reply #13 Top
a further thought, would it be sensible to post simple instructions on finding / using this on the windowblinds newsgroup?

lots of people using win9x are still posting about the fact that the skins list in displays properies isnt alphabetical. using the "big" front end gives a sorted list, solving this problem most neatly.