Brad Wardell's Blog


One week away..

Published on Wednesday, March 16, 2005 By Brad Wardell In GalCiv II News

We're about one-week away from the first BETA. It's going to mainly be about figuring out what % of systems currently out there blow up on loading it (don't worry, we don't really mean blow up, it's more of an explosion type scenario <g>).  But it'll give players a chance to check out what we're doing and let us know what works and doesn't work and what direction they'd like to go.

Anyone who has an active TotalGaming.net subscription OR has pre-ordered Galactic Civilizations II will get the beta.  However, the day AFTER the beta, new peole joining will go back to pre-ordering until Beta 2.

Incidentally, DesktopX 3 was released today which is what we used to design the UI. It doesn't just let people change the look of the UI, you can move everything around, resize, etc. with it. So if you don't like the way we've done the graphics, you can change them yourself.

DesktopX 3 available for download

Published on Wednesday, March 16, 2005 By Brad Wardell In WinCustomize News

Add animated icons, stock tickers, system resource monitors, picture frames, and much more to your Windows desktop with Stardock's DesktopX 3. 

DesktopX is a program that enables users to add all kinds of new and interesting things to their Windows desktops.  By default, Microsoft Windows only supports static images on the desktop called "icons".  DesktopX can take your desktop to the next level by allowing user to put desktop objects and widgets on it as well. It also supports creating entirely new desktops from scratch.

DesktopX 3 is a major improvement over previous versions. Not only does it have vastly more features than previous versions, it has been re-designed to separate the user portions from the content creation portions.  Previously, someone who wanted to simply add "widgets" to their Windows desktop also had to interact with DesktopX's powerful, yet easy to use, developer environment which tended to overwhelm new users.  With DesktopX 3, the features of the program have been streamlined.

Major user features of DesktopX 3 include:

  • Import "objects" onto the desktop that can be everything from animated icons to mini-applications
  • Load a .Desktop file that can replace your existing Windows desktop with something completely  new
  • Load a "widget" which is a mini-program that can run on any system that has DesktopX installed.
  • Includes dozens high quality widgets and objects for users to instantly start using
  • A simple "widget manager" that uses hardly any memory that allows users to keep track, load, and unload widgets
  • Thousands of third party desktops, objects, and widgets to download
  • Uses relatively little memory or system resources

Major developer features of DesktopX include:

  • Built in development environment makes it easy to create objects, widgets, and desktops
  • Use scripts or plugins to add features to your creations
  • Animation, transparency, shadows, and similar options are built in
  • Creations can be exported as objects, widgets, or desktops depending on the developer's needs
  • Most creations do not require any programming at all
  • JavaScript and VB Script both natively supported
  • Direct support for Windows APIs such as WMI allow for much more sophisticated creations
  • Native support for object "States" which can be configured via a GUI (makes development much quicker and easier of complicated things)
  • Custom preference dialogs can be created via scripts for widgets
  • Third parties can extend DesktopX's APIs through plugins (developers aren't limited to what features we've thought of).
  • Native support for accessing the Windows clipboard
  • Widgets can be exported as stand alone programs called "gadgets" with DesktopX Pro!

DesktopX 3.0 comes in 3 flavors: DesktopX Client which is for end users who just want to run widgets, objects, and desktops created by others.  DesktopX Standard which adds the development environment for creating/modifying widgets, objects, and desktops. And DesktopX Pro which enables developers to export their widgets as gadgets.  Unlike widgets, gadgets can run on any Windows 2000/XP system without requiring DesktopX (or any other special software) to already be installed.

A shareware version of DesktopX 3.0 Standard is available for download at http://www.desktopx.net.  The standard version of DesktopX is part of Stardock's Object Desktop, a suite of desktop enhancement programs that also includes WindowBlinds, IconPackager, ObjectBar, RightClick, WindowFX, SkinStudio, and much more.

Get DesktopX:

Screenshots:

Related articles:

Freeware users vs. Freeware idealogues

Published on Wednesday, March 16, 2005 By Brad Wardell In Industry

In my last article I talked about why freeware usually doesn't succeed as a long term competitor to commercial software. In a nutshell it was because freeware authors tend to start their programs because it interests them, then they stick with it because they feel a loyalty to their "user base" but then eventually stop developing either from lack of time, losing interest totally, or (very commonly) because their "user base" abandoned them suddenly.

Now, predictably, some freeware advocates pointed out a bunch of successful "freeware". They apparently didn't understand the point (since after all, the most popular freeware programs in the Windows customization community are made by us so I obviously don't have some axe to grind against freeware programs). And open source programs aren't necessarily freeware (nor can you really compare a "freeware" program created by "Joe Developer" with some browser created by a team of professional, salaried software developers.

I personally use freeware whenver I can. I'm cheap. If a free program will do the job, I'll use it.  But on the other hand, if I have something I've got to do and the freeware won't do the job, I'll gladly pay money for it.  (case in point, I'm about to stop using free CamStudio for my video demos and go to HyperSnap's product because CamStudio's too flakey).

Every community has its zealots.  The point I was trying to illustrate is the inevitable EFFECTS of zealot behavior. In this case, I was pointing out how the fickle nature of freeware communities tend to drive freeware developers into the commercial camp.

Let me give you a common scenario (this is a fictional example):

Joe Developer gets interested in making a really cool calculator program. He's interested in making such a calculator but decides one day to put out his first "Beta" version onto a site he frequents called "NeatGadgets.com".  Within a few weeks, a forum is made for him on NeatGadgets.com and a bunch of "regulars" start praising him.

Pretty soon every time he releases a new version of his calculator, some of the people from his "community" go out and start posting and about it elsewhere. They evangalize it.  They tell Joe how great he is and how much better his program is than commercial calculators are.

Over time, Joe gets busier and busier with other things but keeps at it because he feels responsible to his "customers" (the community). He doesn't want to let them down. So many weekends are spent putting in request X and Y that came in from his "customers". At this point, his calculator is pretty damn impressive. It's very feature rich, very solid.

Then one day, he logs on, and a new guy, Bill Developer, has released his first build of his free calculator. It's rough and doesn't do anything that Joe's calculator already do and do better. But suddenly, many, even most of Joe's "community" flocks over there, some of them saying how much better it is than Joe's calculator. And in fact, suddenly, when Joe makes a new release, no one even comments on the new release or reposts about it on other news sites. In fact, some of them will come on and say "Joe's Calculator is crap, you should try Bill's calculator!"

Now Joe feels hurt and betrayed. He thought of these people as his friends, his supporters. But they weren't really supporting him or his program. They were simply supporting the CONCEPT of free software and for them, the goal is to have LOTS of free software in quantity.

Joe then calls up Commercial Calculator Corp. and starts talking to them.  Pretty soon, a new calculator is being made that's even better because he's being paid to do it and he already liked doing this stuff anyway. And the free calculator disappears or lags and those same people who had previously betrayed him are calling him greedy or worse.

I've seen that scenario play out so many times over the years that it's amazing how predictable it is.

In the commercial world, what do I care if some guy like Byron is running around pissing about some half-baked freeware program.  If someone likes my work, they hopefully purchase it. If they later decide something is better, that's fine, they can go use that.  

In the commercial world, there's a certain..fairness. While I hope that our customers will be loyal to us, I don't expect it. If another product comes out and they switch to that, I am not going to have my feelings hurt in the same way that I would if I were devoting countless hours of my free time to them.  

What happens is that many freeware developers start to mistake their supporters as customers. And the "currency" their customers pay them in is through their support, appreciation, and accolates.  So when, inevitably, some/most/all those supporters instantly flock to the latest/greatest  freeware gadget, the developer feels hurt and betrayed. He can't get that free time back. He has nothing at all to show for his lost weekends and nights.  The commercial developer, by contrast, might still feel a bit of a sting but at least they were able to earn a living or at the very least be able to have bought a new computer or paid for a trip to Disney World or whatever. 

The OS/2 market was full of similar zealots. They would lobby for a product to be made for OS/2 and then not buy it when it came out. They didn't really want the product to use, they just wanted to add another notch to the OS/2 software catalog.  The freeware idealogues are much the same way. They don't really care about the actual program or the developers. They just want to (as some people in related threads) to list off a bunch of quality freeware programs that exist. 

DesktoX 3 Quick Start Guide

Published on Wednesday, March 16, 2005 By Brad Wardell In DesktopX Tutorials

Quick Start

Spring 2005

(c) 2005 Stardock Corporation

General overview

Stardock DesktopX is a program that is designed to allow users to put useful and interesting things on their Windows desktop. By default, Windows only supports putting little static pictures called "icons" that act at "short-cuts" to other things.  DesktopX allows you to add desktop objects to your Windows desktop that can do almost anything one can imagine.  These objects can be combined together to create mini programs or used to create an entirely new desktop. 

When the content that one makes with DesktopX is exported, it can come in the form of a DesktopX object pack, a DesktopX widget, or as a .Desktop file (for replacing the desktop).

This Quick Start guide is designed to walk users through the basic elements of DesktopX.

The DesktopX User Interface

When you load DesktopX you are presented with this user interface.  If you are using the DesktopX Client, the last option "Create" will not appear.

The Widgets option allows user to load up DesktopX content that was exported as a mini-program called a widget. Widgets live on your desktop but behave like small Windows programs. They tend to take up less memory than a normal Windows program and do things like provide system information, grab data over the net, perform simple utility services.  But in truth, a widget can pretty much do whatever the person who makes it can imagine. But think of widgets as "mini programs". These are .EXE files.

The Load Objects option is designed to import a desktop object onto your existing Windows desktop. Things exported as objects tend to be more along the lines as "super icons". Things that do more than your Windows icons but aren't really applications.  A "Recycle bin" object that tells you how many items are in the recycle bin would be an example of a desktop object.  Or an Internet Explorer "icon" that changes its size and shape when the mouse moves over it would be another. These are .DXPack files.

The Load Desktop option is designed for users who want to load an entirely new desktop created by someone else. Your existing Windows desktop probably has the "Start bar" at the bottom of the screen and a number of icons on it.  People from around the world have their own ideas on how the Windows desktop should look and work and have used DesktopX to create them and then export them. These are .Desktop files or .DXThemes files.

Using Widgets

When you choose load widgets, the DesktopX Widget Manager is run. This is a simple program that resides in your system tray to make it easy for you to access and manage any running widgets. You don't need it to load widgets, it just makes it convenient to organize what's running.

Widgets are designed to exist on your desktop but they have also been designed not to clutter it up. You can assign hot-keys to your widgets that will make them show or hide. They default to F9 (to activate a widget) and F10 (to toggle showing or hiding them). Note that you may have to change these defaults as other programs may be reserving them (such as Multiplicity which reserves F10 for switching desktops).

Widgets also have a properties dialog. Right click on any widget and you can access its properties dialog.

Typically, a widget has at least two tabs on its properties dialog: Appearance and General Settings.  The appearance tab lets you control how the widget looks.  The General Settings lets you control what hot keys will activate it. Some widgets have a "Preferences" tab that is widget specific.

Using Objects


Quick Tip:

If you want DesktopX's development environment to be the default DesktopX mode when you import objects or load desktops, choose "Create" to load up the DesktopX development environment and then go to the "Preferences" tab and click on the "Make DesktopX Builder the default program for loading .dxpacks and .desktops"

When you use to load an object on to your desktop, it will open up your objects directory. Double click on the object you want and it'll add it to your desktop. At that point, if you are not running DesktopX, it will load up the DesktopX run-time (client).  DesktopX client allows users to remove objects or set the target of the object. But to do more than that, users need to go into the DesktopX development environment (by choosing the "Create" option).

Using Desktops

Using a desktop created by another person can be quite an experience.  Most people who make desktops create them for themselves that they happen to make available on sites such as www.wincustomize.com for others to use.

That means that they tend to be resolution specific (common resolutions being 1280x1024 for instance).  If you're not running at the resolution specified by the author of the desktop, you will probably run into problems.

Many desktops are resolution independent. But when downloading desktops, just be sure you look to see if it specifies a particular resolution.  If the desktop hides your Start bar and desktop icons you can access your key options by right-clicking on the Windows desktop.

Creating or modifying objects, widgets, and desktops

Creating or modifying things in DesktopX is quite easy. However, it goes beyond the scope of this Quick Start Guide.  A few tips though for that:

  • Holding down the CTRL key while left clicking on a given item will allow you to move it around (Ctrl-left click dragging).
  • Holding the CTRL key is also the default key for interacting with ActiveX controls.
  • You can also hold down the CTRL key to select multiple objects.
  • If drag selecting multiple objects has stopped working, odds are some other program has hooked the mouse during that time. To enable DesktopX to re-hook the mouse, restart it by right clicking on the DesktopX icon in your system try and choosing "Restart DesktopX".

Other Resources on the Net

Why freeware nearly always loses in the long run

Published on Tuesday, March 15, 2005 By Brad Wardell In Industry

In various software community niches I've been described, over the years, as the software equivalent of Emperor Palpatine from the Star Wars movies. I find outstanding software developers who are happily making freeware programs and lure them to the dark side of the force -- commercial software development. 

And so the belief goes that if only the evil bastards at Stardock weren't plucking these Jedi knights of freeware and corrupting them that there'd be these wonderful freeware programs.  Or put another way, that the programs that we make that have one of these star developers involved would have come out, as if by magic, as freeware if it weren't for our "greed".

The reality, not surprising, is more complicated than that.  The life cycle of a typical freeware developer goes as follows:

  1. They start developing a program because it's something that interests them personally.
  2. They continue developing it because they appreciate the accolades, appreciation, and attention they receive from whatever on-line "community" it is involved in it.
  3. They stop developing it either because they've totally lost interest, have found it extremely "not fun" to keep updating, or because the once supportive "community" has cast them aside for the latest/greatest "freeware" goodie.

As a commercial software developer, I've watched this cycle over and over.  Whenever a "free" program begins development in the market we're in, people will say "Aha! Now finally we'll have a free alternative to program X!"  What they don't know is that we use the same strategy over and over with freeware "competition"-- we wait them out. 

We can always wait out the freeware author because either his program no longer hold his attention in competing with "real life", or it'll become too tedious to keep enhancing it, or (quite commonly) the very people who once went around spamming for them on every forum telling the world that it was the greatest thing have turned around and betrayed them by tossing their support out in favor of some even newer freeware program, even if it's in competition with their freeware program.

I've seen it over and over again.  What often drives talented software developers to come to us in the first place is a feeling of betrayal at the hands of their "supporters". They'll make something for free, put it out there, and for awhile, they'll get support, accolades, and attention.

But much of that early support comes from people who worship freeware as an ideology. They use freeware regardless of whether they could afford commercial software (even when it's better) but because they consider commercial software the bane of the universe that must be fought against. But freeware ideologues are a fickle lot. As soon as the next "hot" thing comes out, off they go.  Some of the very same people who were once spamming forums talking up freeware program X will later go back and spam for freeware program Y and even mention that Y "kicks the crap out of X!"

This is something we've seen since the beginning of our company (ten years ago). But rarely is it made more vivid than a recent episode involving one of our young developers who has spent a sizeable chunk of his young life selflessly making freeware programs to help support a "community".  When we announced ObjectDock 1.11, a FREE program, it was spammed, by people who originated from the same "community" that once claimed undying love and loyalty for this program, in favor of people who want people to try out some other (newer, but far less featured) dock program. 

The reaction of some of our developers to such spamming is "Are you guys high??" because ObjectDock, at this point, isn't just slightly more mature, feature rich, etc. (and did I mention free?).  It's massively more feature rich, uses less memory, faster, more customizable, etc. than anything else available.  That's the benefit of having worked on it for 3 years steadily.  But such is the fickle nature of those with the "freeware ideology" that they'll latch on to the newest thing.  Their loyalty was never to the freeware developer or the freeware program but rather the freeware cause.  Simply put, ObjectDock, while free, got their attention already. Now it was time for them to move to some other thing. 

I've seen it so many times. Developers find it rather cutting when they discover that there's very little loyalty or depth of support for them personally or their programs.  That the "support" freeware developers receive from on-line communities is often (not always) because it is free and new and nothing else.

Because the cycle repeats and is so predictable, commercial developers rarely fear from freeware developers because it's only a matter of time before that freeware program dies out.  The life cycle of the freeware program will play out and the commercial program will be the one that continues to be updated, enhanced, and available while the freeware developer often ends up becoming part of the commercial development team.

In the long-run, it's about incentives. When a software program becomes "mature", enhancing it becomes quite laborious. There has to be some incentive to keep updating it at that point.  Commercial software provides a pretty straight forward incentive -- financial income.  But glory, accolades, and community support can make a big difference as well.  Luckily for us sith lords, community support is nearly always fickle, ultimately turning that Jedi freeware developer into a Sith commercial developer.

Apples discovers two button mouse

Published on Tuesday, March 15, 2005 By Brad Wardell In WinCustomize News

To better assist Windows users wanting to convert to the Macintosh, Apple is apparently working on a two-button mouse.

Meanwhile, Las Vegas odds makers are currently taking bets on how long it will take for Macintosh advocates to claim that Apple invented the two-button mouse and Microsoft and "PeeCee" users merely copied it from them.

DesktopX 3 User Guide

Published on Tuesday, March 15, 2005 By Brad Wardell In DesktopX

Normally we use Adobe Acrobat for creating our documentation.  But for DesktopX 3, we're looking at switching over to MHT.  It seems to be more flexible than Acrobat and the output seems quite good still.

Click on the link below to check out the brand new DesktopX 3 User Guide.

Animation on your desktop

Published on Monday, March 14, 2005 By Brad Wardell In WinCustomize News

For those of you who have ever wondered about having animated items right on your Windows desktop, DesktopX makes doing this easy. Read this guide that goes over how you would go about doing is using animated GIFs as the example.

Microsoft to abandon passwords

Published on Monday, March 14, 2005 By Brad Wardell In WinCustomize News

Microsoft has revealed at a security panel at CeBIT that it is preparing to dump passwords in favour of two-factor authentication in forthcoming versions of Windows. Detlef Eckert, the senior director in charge of Microsoft's Trustworthy Computing initiative, did not specify which form of two-factor authentication would be used in the next edition of the company's operating system, codenamed Longhorn.

But he said that the code would have vastly improved handling of technologies including smartcards and security tokens. "I believe that the time of password-only authentication is gone," said Eckert. "We need to go to two-factor authentication. This is the only way to bring the level of trust business needs." The panellists were in broad agreement that better digital identity is essential for the future development of e-commerce. RSA Security chief executive Art Coviello suggested that the effects were already being felt, pointing out that some Australian banks have recently pulled out of planned web services because of security fears.

Hat tip to Neowin.net.