This is what my site looks like in the form of a word cloud (make your own at wordle.net).  I suppose I look like a Microsoft junkie at the moment… Let me assure you that this is not the case. I’m a firm believer in the right tool for the right job.

That said, most of my time is spent in Photoshop and Illustrator as of late. I’m almost beginning to feel like a traditional graphic designer again. I’ve got some pretty nifty stuff coming up for U-Haul, and it isn’t even SuperGraphics related! I’ve also been working on a promo piece—for print even—for a web application shop out in Mesa.  I’ve been busy!  I love it all!

Good things coming up… Stay tuned!

That’s right other designers, be jealous.

Problems with Silverlight

Silverlight is currently in version 2.0 beta 2. I had a few small setbacks when they updated to beta 2. First, it did not work on my mac—at all. This issue has since magically fixed itself, though I’m still not sure how Microsoft did it.  I suspect that Microsoft covertly patched it without my knowledge.  In any case, this is no longer an issue. the second issue I had was with the fact that beta 2 will not run Silverlight apps created using beta 1.  I suppose that’s why it’s “beta” and not a full release.

These are problems that should not happen again. It’s good that I haven’t been having these problems on a live web site. I can only imagine how frustrating it must be for companies who have Silverlight applications deployed already, like the Hard Rock Cafe Memorabilia site.

Things I love about Silverlight

Despite the minor problems I’ve experienced with Silverlight, There’s still plenty to love about it. My absolute favorite part is the way animations can be easily reused. In Flash, if I want to fade something to grey, I have to create a movie clip that fades it from its original color, to grey. I have to do this for every color I want it to start from. So, to fade something from red to grey, and later from green to grey, I have to create 2 seperate movie clips. In silverlight, it will make an animation based on what state you want to end the animation at. to use the same example, I need to only create one animation, at the end of which, the object (regardless of its original color) is grey. Silverlight will do this with all sorts of different parameters, like size, shape, position, angle, or anything else.

I also never thought I’d find myself liking to use XAML, but it really is nice to be able to see under the hood of the animations. Has Flash ever done something completely bizarre to you and you can’t figure out why everything’s broken? That doesn’t really happen in Silverlight—you can actually see what’s not working. furthemore, when doing a build (think of it like publishing in Flash) and you have errors, the errors are generally helpful, and well documented.

Things I hate about Silverlight

Now, I can’t let Silverlight get off that easy, now can I? There are some serious issues that need to be resolved before Silverlight can call itself a legitimate competator with Flash. The first is that it needs a decent designer tool that can help designers actually start their animations and do some basic scripting. Currently, you have to do this by editing C#, Javascript, or VB code, unless you want all your animations to begin as soon as they load or at a set time after loading; You can’t trigger animations on a main timeline, because there is no main timeline. Expression Blend is pretty nice when it comes to creating XAML code, but leaves much to be desired in terms of a code editor. It doesn’t even do any sort of intellisense! Flash’s Actionscript editor is much easier to use, even as a designer. I don’t want to hire a developer every time I need to create something simple in Silverlight, but as it is, it’s too difficult to implement for a designer with moderate programming skills, that doesn’t want to learn another new language (I had to pick up some C# skills for my latest project).

Secondly, Microsoft really needs to get Silverlight installed on people’s machines. This would be much easier if they’d make sure people didn’t have problems installing, and if the beta versions would be compatible with each other. I say this because I know several people who were turned off from Silverlight from the get-go because they had installation problems with Version 1. The current version had some issues transitioning between beta 1 and beta 2, but I suppose it’s forgivable because they’re calling it a beta.

Conclusion

I’ m not about to give up on Silverlight. I’ve actually been able to do some good work in it (links coming soon). However, it remains to be seen if it can actually catch up to the Flash install base, and declare itself a legitimate competator to Flash.

Now, I don’t intend to beat a dead horse and continue whining with all the other web standards evangelists about why people don’t update their browser or switch to something better.  I want to ask a question – why bother supporting outdated and inferior web browsers?

Think of your users

Consider this: Many of your users are not aware of what a web browser is. These users normally just double-click on the icon on their desktop marked “Internet” and that’s all they know.

I know we’ve all thought about it at one point or another — locking these users out of our brand new web site with a pop up or a snazzy javascript error message. It would be so much easier than actually working to make the new site work for them as well, and besides, who wants some ugly IE6-only code mucking up painstakingly crafted HTML and CSS?

Wheel chair ramps

Brick-and-mortar shops are required by law to have wheelchair accessible entrances so people with disabilities can shop there. This sort of law doesn’t apply to the internet (yet), but we don’t need a law to tell us that we want everyone to be able to get to our sites. If we exclude people who use “handicapped” browsers, we’re looking at lowering the effectiveness (and profitability) of our sites significantly.

Think about it: If Wal-Mart built a door that somehow kept disabled people out, they would reduce their profits by a significant margin. Less people entering means less people buying. The same principle applies to web sites.

Conclusion

We designers should be bending over backwards to make sure that everyone, regardless of their browser of choice, can access and use our sites. I’m getting a little tired of hearing (and occasionally saying) “when can we stop supporting IE6?” The answer is when people stop using it — which may be quite some time away.

So, I’m just getting started with trying to drive traffic to my site, since it’s (mostly) looking good and working. I’m finding that I’ll need to write a bunch of comments on people’s blogs, link to ‘em in my links, try to get my site published on CSS galleries and all sorts of fun stuff. I’m sort of getting excited just thinking about it!