Back in January of last year, I started work on the Six Minutes To Release website using Silverlight. It... didn't go so well. People couldn't use it on Macs, and there were other fugly things about it I didn't like. I ended up abandoning the project and coding it in straight ASP.Net.
Turns out that the XAML experience I got from working on it the first time through the SMTR website came in handy. The Rawr project is using Silverlight for its next major release, Rawr 3. Having taken on the protection paladin module, I was able to write a needed piece for that module to work in Rawr 3 in about 3 days on and off. Of course, the stumbling of not having touched it in nearly 2 years took me some time to get past, but once I did it was smooth sailing.
There's a few things I don't like about it, though. Rawr is going to release a Silverlight web release and a WPF application release. The problem with the two releases is that the XAML used in each is not necessarily compatible with each other in all cases. This results in being unable to use certain features, such as StringFormatting. We also have to use a cheap preprocessing approach to be able to compile the same XAML file in both places.
Is it me, or could Microsoft have done a better job of streamlining the two versions? Why even have two versions of XAML? It seems like a lot of extra work for similar functionality that could be done all in one place.
In any case, I've put a lot on my plate, and I've devoted this weekend to getting it out. Up next, SMTR's new raid performance reporting, which is almost done. Should be fun.Labels: Coding, Gaming, Rawr, Silverlight, Six Minutes To Release, World of Warcraft, WPF, XAML
0 Comments
|