Before Windows XP came on the scene, ObjectBar was one of Stardock's popular programs. OB had the capability to emulate the then new Luna bars. Although I wasn't a part of the skinning community at that point, and I'm still a wee lil fledging compared to most of the skinning gurus who I chat with, but I've learned the history and reputation of OB fairly quickly.
And what I have learned is this: ObjectBar is a generation behind the current Stardock software, and newer pieces of ObjectDesktop can do all OB can, plus more, such as DesktopX or ObjectDock.
Allow me to justify this claim by describing the negative aspects of OB which I encountered during my week-long odyssey with it. The application itself has an old, chunky feeling to it, and its interface is convoluted and very un-user-friendly. From my experience with coding the skins in SkinStudio, that part of the process truly is a generation behind. Most skinners and even Adam Najmanowicz (the head programmer for SkinStudio) did not know that animation was possible with OB, but after quite a lot of trial and error and some help from the IRC, I squeezed an 10 frame animation out of it.
Now, before I'm labeled as a nay-sayer of OB, please realize that I'm not. I would not have spent my free time during spring break for shits and giggles (pardon the profanity), but I intended to start to learn how to program SkS. I believe that OB has a future, but it lies in a different path of where it's headed now.
A growing sector of the skinning industry, if I may coin it as such, is shell replacement. I'm not talking about WindowBlinds, I'm talking about applications which extend, surpass, and murder the functionality if the RAM intensive Windows Explorer. Many users are starting to put an end to "explorer.exe" and firing up programs like LiteStep, HoverDesk, GeoShell, and AstonShell.
What is Stardock's response to these? DesktopX. It has infinite capability unlike any other program of its kind, but in in order to unlock it, one must usually possess that key knowledge of programming. To be honest, the average user of DesktopX won't be able to code his way to a better desktop. THIS is where ObjectBar comes back into play. With a revamped GUI, more features, and flawless shell replacement, OB can be resurrected from the Windows 2000 era.
DoctorNick's Prescription to Revive ObjectBar:
1) Marriage with DesktopX
2) Total Revamp of GUI
3) Seamless WBA Integration
4) Skinning Program: BarEdit
5) Updated SkinStudio Features
6) Absorb TabLaunchpad
7) Widgets & Plugins
8) Advanced Help System
Now I'll elaborate on each of these:
1) Marriage with DesktopX
As mentioned before, DX has the ability to eclipse OB in terms of functionality. At this point OB seems like it could simply be a plugin .dll for DX. Stardock must decide- will OB lie in the shadow of DX? I say no! OB has the potential to rightfully be DX's equal. OB and DX can easily emulate the Windows shell, with much less RAM plus the CPU, since neither program paints itself while invisible on the screen. ObjectBar needs to become the substitute for that chunky lump of blue and green.
THE KEY is that OB must be easier to use and able to be configured as simple as DX is. Only other added features can elevate OB's status, and if OB 2.0 is missing them, if there even is going to be a 2.0, DX may end up annulling any relationship that might have existed.
2) Total Revamp of GUI
The first major flaw is OB's interface. The clunky and confusing system disallusions many users. As skinning becomes more mainstream, the users will require simpler and more efficient interactions with the programs themselves. A perfect example of this is tge WindowBlinds Configuration Dialog, which superfically displays the easy ad basic features. Digging a bit deeper shows the more complex tweaking. OB needs to re-sort itself in thus manner.
A second way to fix this is to redo the actual graphics if the program. A nice looking program with some sharper icons is definitely needed. Specifically, higher quality icons for bars, containers, and other special items may cut through the fog surrounding the OB Theme Editor.
3) Seamless WBA Integration
This will be the newest feature to get OB on the normal Stardock's user's desktop. Now the current OB has a very limited integration system. It basically sucks your WB taskbar and start menu and turns it into the pre-XP skin of XP Jeans. The result can be compared to baking a loaf of bread and out of the oven pops out bagels. It usually turns out to be the ugly cousin your WB's start menu (I love bagels...I was focusing on the hole in the middle of both).
The cure for this will be a perfect transition of WB into OB. By reading through the .wba in SkinStudio, OB can perfectly emulate the Start Bar that you want. Hopefully this process can either be embedded into the .WBAs or it can be processed with the click of one button. This will take the RAM load off of WB (freeing up more for the animations, which are now near required for high quality skins), plus add special functionality in the form of plugins.
4) Skinning Program: BarEdit
Here's my most bold proposition, but I believe that this aspect may be able to bring ObjectBar to the mainstream. Instead of overlapping OB features with SkinStudio, devote its own developing application towards the future of OB. (I've named it BarEdit simply to just call it something at the very least) WindowBlinds and IconPackager have their own creation programs, so why not OB? It will obviously be rooted in its SkS roots, but this may be the solution to shell replacement. New and unheard of features in SkinStudio could be found in BarEdit. This could even replace the dreaded OB Theme Editor and become the home to those complex options found in it.
A separation from SkS could prove to be factor which restarts skinning in OB. Currently the processes for skinning OB are the most unknown sector of SkS. Until I sat down to skin, I had no clue how to create OB skins, specifically the bars themselves. I expected to find an IconPackager style Package Builder, or a built in system a la DesktopX. An easier system that mixes the assisted coding of SkS and the testability of DX may be the saving grace of OB.
5) Updated SkinStudio Features
This may seem contradicting with my previous point, but it can be worked in with or without BarEdit. Recent advances in SkS have led to toolbar icons, file animations, and much more. OB should be able to have these features as well. For example, the skinning aspect of OB desperately needs better font styles and PNG or TGA support.
6) Absorb TabLaunchpad
WinStep's WorkShelf tool has a serious competitor: TabLaunchpad. Since only ODNT subscribers can access this, its usefulness isn't well known. I’m not that familiar either with it, but I’m going to play with it more. The program could be able to be skinned, and if combined with OB, the usefulness of could make Geoshell obsolete.
7) Widgets and Plugins
These will hopefully be Sysmetrix like plugins, plus it'll borrow certain DX plugins.
8) Advanced Help System
This final feature will be a la SkinStudio once again. Just like the help box in SkS, OB needs something of the sort either built into the GUI or in the form of tooltips.
Hopefully these with some Stardock magic can bring back OB. Please feel free to add your own hypothetical features, and remove or append my suggestions. Constructive criticism will be appreciated. Thanks or reading, and Viva La ObjectBar!
-Nick Quaranto