WindowBlinds Lite?

Just curiosity more than anything, and I suppose this question should have probably been mailed to Stardock, but anyway...

Has there ever been thought given to a "lite" version of WB? And when I say lite, I mean a very minimal version of WB. Not a uis1, but a full implementation of WB that ONLY skins the windows themselves. No StartBar, no XP extras, no menus - just the windows themselves.
The reason I ask is simple. For those who use shells, and shell enhancements, there's really no reason for these other parts to be skinned, and no reason to use those resources for something that the user will never see. Whether it's Litestep, Nextstart, Hoverdesk, DX, Objectbar, or any of the many other choices involved, those other parts seem to me to be a waste of resources. I'm not saying that skins should be created just for "WB lite". I see no reason why this possible version shouldn't simply ignore those extra parts.

So, am I missing something obvious in asking this?
Anyone else see any merit in this request?
Or should I just wait for the rocks to start flying?
13,023 views 26 replies
Reply #1 Top
There has never been a WB Lite as far as I know. WB does have a setting, however, to not skin XP specific features. If you check that off, resources will not be devoted to skinning your taskbar and start menu.

Powered by SkinBrowser!
Reply #2 Top
i would like that too. but i don´t think this will happen. i´ll wait until Nivenh finishes integrating windows skinning into the Bluebox shell. this will be an extremely lightweight, vector based way to skin windows. until that i´ll stick with Illumination.

btw: a wonderful WindowBlinds skin, that does not care about the Exploder shell has just been released yesterday. so get jealous now http://www.deskmod.com/?show=showskin&skin_id=14722
Reply #4 Top
Sorry, Mike.
I guess I didn't explain myself properly. Actually, I've been using WB on and off since v.50, and while OD did release a version called WB Basic (which really wasn't what I meant, but hey - the name sounded enticing ), I guess I was just addressing the issue of whether Stardock had considered a stripped down version. And when I meant skinning the taskbar, it wasn't just XP I was talking about, but Windows in general. Whether it was 95, 98, NT,2K, or XP, if you're using a shell app, there IS no start bar, per se - unless you create something to simulate it.

And Moshi, I agree, and while I'm looking forward to what BlueBox (or Blackbox for Windows, for that matter)has to offer, I'd still like to have one app to handle the windows skinning no matter what program I happen to be using.

And Crae is always looking for a scoop...
Reply #6 Top
There's options in the WB settings to not skin an awful lot (each can be individually set)

Skin Standard Parts:

Standard Window Buttons
Taskbar Buttons
Toolbar Buttons

Advanced Controls:

Menu Borders
Progress Bars
Tabs
Scrollbars
Statusbar
Menu Backgrounds

Powered by SkinBrowser!
Reply #7 Top
There is an OEM version of WindowBlinds, but I'm not at liberty to say more about where it is being used this week (ask again in a week or two).

It's basically buttons, titlebars, borders, and the taskbar. Streamlined UI. And then more fully skinning theme-aware apps on XP as well.

It is also constrained by what skins it can run (depending on the customer needs).

But, that's what it's for. Not meant to be a regular WB where you can pick any skin.

For what you're looking to do, between the options pj posted and the per app settings, you're pretty much covered with what you have right now.

Reply #8 Top
looks like there will be an alternative soon check the BlueBox site for a wip screenshot. http://bluebox.lokai.net/
Reply #9 Top
Actually, I know what you're talking about Elwin. I use NextStart all of the time (well, except for when I'm using DesktopX) and so I don't ever see a taskbar, systray, start menu, etc. I've done a few WB skins in the past (when they were simpler), but now I think I have a mental block on them because there are just so many things to skin it's rather intimidating. I know that realistically it can't be too bad because some people can seemingly whip out one or two WB skins a week.

If there were a "light" version my guess is that I'd use it more often and make more skins for it. Mostly because (as you described it) it would do what I need and no more.

However, the problem is that these skins would only be of use for other "WB light" users. If you wanted a full-blown skin, you'd be unhappy with the light version since it would leave out many things. What would happen next wouldn't be pretty either - you'd get inundated with emails saying your light version was nifty and please make a full version.
Reply #10 Top
I'm not sure why you don't just turn off the features you don't want.



Powered by SkinBrowser!
Reply #12 Top
Another way of looking at it would be that die-hard users of Litestep, Nextstart, Hoverdesk, DesktopX, etc. are less likely to make WindowBlinds skins because they'd spend hours and hours skinning something they never use or see.
Reply #13 Top
A skin that is not using a given UI element doesn't use resources for it. So, you are free to make a skin with just the features you like. Alternatively you can also remove features from a skin by editing it.
Reply #14 Top
forget i asked about that. just downloaded the pre-alpha version of bwm (released today) and am drooling. still has a way to go, but it wont be that long. it actually works pretty good

so no reason to rip on StarDock, you did NOT disencourage freeware/Open Source developers.
Reply #15 Top
Well, I guess my way of thinking was similar to idea of "why load Microsoft Word when all you really need or want is Notepad?"
Reply #16 Top
Here is a fully functional UIS1 skin that I made (the Windows 3.1 skin):

---
[TitlebarSkin]
SkinName = Windows31
SkinAuthor = You
ActiveTitle=Windows31\horizontal.bmp

[Borders]
vertFrame = Windows31\vertical.bmp
HorzFrame = Windows31\horizontal.bmp
TopTopHeight = 24 ;start tiling 24 pixels from top.
TopBotHeight = 24 ;from bottom.
LeftTopHeight = 24 ;from top left (downwards)
LeftBotHeight = 24 ;from bottom left (upwards)
RightTopHeight = 24 ;from top right
RightBotHeight = 24 ;from bottom right
BottomTopHeight = 24 ;from the bottom in on right
BottomBotHeight = 24 ;from the bottom in on the left (yea, these could be named better)

; We want our title bar text to be moved over from the left
; by 30 pixels and there are 4 title bar buttons.

[Caption]
TextLeftShift = 30
ButtonCount = 4

; Our close button

[Button0]
XCoord = 0
YCoord = 3
Align = 0 ; align from left
Action = 0 ; close the window
ButtonImage = Windows31\sys.bmp
Visibility = 0 ; always show it.

[Button1]
XCoord = 19
YCoord = 4
Align = 1 ; align from right
Action = 1 ; maximize the window
ButtonImage = Windows31\max.bmp
Visibility = 20 ; show only if there is a maximize button.

[Button2]
XCoord = 38
YCoord = 4
Align = 1
Action = 2 ; minimize the window
ButtonImage = Windows31\min.bmp
Visibility = 22 ; show only if there is a minimize button

[Button3]
XCoord = 19
YCoord = 4
Align = 1
Action = 1 ; restore the window
ButtonImage = Windows31\restore.bmp
Visibility = 3 ; show only if there is a restore button.
-----

Pretty small.

Powered by SkinBrowser!
Reply #17 Top
you are right.

i included something similar (not UIS1 probably, but stripped to the bone) in my Mas Siemple HoverDesk theme. http://www.deskmod.com/core.mod?show=showskin&skin_id=12677 . i saw no point releasing the WindowBlinds skin alone, so it is just a little extra goodie for the people that read the theme description or explore the theme folder. i doubt anyone uses it though
Reply #18 Top
That was an eFX skin. But yea, other than the title bars/borders a skin author doesn't have to do anything on a WB skin to make it work. It can be as "lite" as you want it.

And check out the size of wblind.dll, it's tiny.

Powered by SkinBrowser!
Reply #19 Top
Moshi....same here with my 'Nijikon Fetchi' LS theme....included a WB skin that is intended to complement the theme, but I didn't bother with the Exploder details, just the 'blinds' themselves...
Reply #20 Top
Actually... there was a WB Lite back in the day. It was called WBLiteFX, I believe. That was back before Neil joined up with Stardock. But it's really unimportant, as it's extremely outdated and therefore pretty much useless. If anyone still even has a copy.
Reply #21 Top
that wasn´t nice Frogboy at least it got inactive states, clikcable buttons and a drop shhadow on the title, hehe

ah, at least i tried. maybe i´ll give it another shot when i upgrade my OS (fingers crossed SkinStudio will work then).
Reply #22 Top
In the screenshot I saw eFX's icon in the system tray.

When it comes to a "lite" version of something there are usually 3 main reasons to request a "lite" version:

1) The lite version would use less ram
2) The lite version would be faster
3) The lite version would load faster

Item #3 doesn't really apply to GUI skinning. On item #1, WindowBlinds uses a fairly trivial amount of ram (how much ram does a scrollbar take? 5K?). And as for the big one - speed, that doesn't really come so much from # of items skinned but techniques used. For instance, compare WindowBlinds 3.4 to say eFX or Chroma or Bluebox.

WindowBlinds 2 was about twice as fast as WindowBlinds 1. WindowBlinds 3 was about twice as fast as WindowBlinds 2. And WindowBlinds 3.4 is quite a bit faster than WindowBlinds 3 (and WindowBlinds 4 on XP may be twice as fast as WindowBlinds 3).

That's the ironic thing about desktop enhancements versus other types of software, they tend to get smaller and faster over time because the success of a GUI skinner is not just what it does but that it has to do what it does without interfering with the primary purpose of the computer.

Powered by SkinBrowser!
Reply #23 Top
3 applies to every window you load, if it has to load anything for it. Some skins load, say, a new copy of notepad almost twice as fast as others.
Reply #24 Top
good point. it would be a good thing to have in skinbench.

Powered by SkinBrowser!
Reply #25 Top
correct, i often "fake" screenies to show more mouse-over states. my bad i forgot about the eFX icon.