Thoughts on the updated Windows Live Essentials Beta

Like many of you, I’ve been using the various Windows Live desktop applications for a long time now. Until fairly recently however, they all looked and felt different from one another. There wasn’t much cohesion. That changed when Microsoft began to make the UIs similar and launched the Windows Live Installer which integrated all the apps. Recently, they gave the suite a better name (Windows Live Essentials) and did even more work to achieve a consistent look and feel. On Monday, they released the latest beta refresh.

windows live

I have most of the apps installed – Messenger, Mail, Photo Gallery, Movie Maker, Writer, and Toolbar. The only one I don’t have is Family Safety. I use Messenger, Photo Gallery, and Writer every day, and the others I use less. The install also includes the Office Outlook Connector, Office Live Add-In, Silverlight, and the Microsoft Sync framework.

I’m fairly impressed with the suite so far, but I still think it’s far from perfect. Here are a few of the things I really like:

  • The new icons look great and are consistent.
  • I love the simplified presence indicators in Messenger (these were in the previous beta too – now there’s just Available, Busy, Away, and Appear Offline).
  • In the old beta, Messenger would always sign out if I switched from Appear Offline to something else. That has been fixed, thankfully. Seems faster too.
  • Writer is easily the best blog publishing tool I’ve ever used. It just works the way I want it to. I don’t know what to say specifically, but it’s awesome.
  • Person recognition and tagging in Photo Gallery absolutely rocks! Very cool feature, useful too.

And here are a few things I really dislike:

  • Photo Gallery is ridiculously slow to load. Once it’s open it seems fine, but from launching the app to being ready to use takes forever. I’ve only got about 36 GB of photos on this machine, so I’m sure there are users with far more.
  • In Messenger, you can no longer control the color of your chat windows. It’s based on the theme/color of the person you’re chatting with. Not sure I like that…it’s a window on MY computer, after all.
  • Speaking of colors, I still don’t like that the apps are inconsistent. I can set Messenger to look black, but Writer looks grey (even though I’ve set the color to be the same as Messenger), and Photo Gallery looks light blue and lacks a color setting button. Why there isn’t a color setting like the one in Office 2007 is beyond me. It can’t be that hard!

In general, I like Windows Live Essentials. It’s definitely something I’d install when setting up a new computer. I look forward to the final release!

All browsers have security issues

ielogo You may have heard in the last day or so about a critical flaw found in Internet Explorer. Microsoft says that “the vulnerability could allow remote code execution if a user views a specially crafted Web page using Internet Explorer.” The risk is mitigated if you run an account with fewer privileges or if you run IE in the High security mode. As always, you should ensure your machine is up-to-date with all of the latest patches at Microsoft Update (you can also find downloads at the Microsoft Download Center).

Unlike most zero day exploits, this one is actually infecting systems fairly quickly. That’s probably why Microsoft decided to take immediate action. As the Zero Day blog points out:

Researching, fixing, testing, and releasing a security patch within an eight day window is an incredible feat — especially given the need to support all versions of IE across all platforms and languages.  This is an ‘all hands on deck’ response from Microsoft – I don’t think we’ll see this as the norm for less critical patches in the future as it is quite disruptive to their own processes.

Make sure you update soon! Like right now!

When a vulnerability like this is disclosed, a common suggestion is to install and use a different browser, such as Firefox. That’s not a bad idea, but don’t think that will solve all of your problems! All browsers have security issues. Yesterday, for instance, Opera released an update to address at least seven security vulnerabilities. And today, Firefox released updates to both versions 2 and 3 to patch roughly a dozen security holes. And no, Chrome and Safari are not off the hook – just two days ago, they tied for last place in a test of password security.

Always make sure you’re running the latest version with all patches installed, no matter which browser you’re using. On top of that, be careful, pay attention, and use common sense when clicking links and opening files.

Edmonton Code Camp 2008

edmonton code camp We’re just over two weeks away from a really cool event for local software developers – Edmonton Code Camp! What is code camp? It’s a free event by developers, for developers. It’s an opportunity for local developers to get together to share with and learn from one another. Similar to DemoCamp, slide decks are frowned upon – show us the code! It doesn’t matter what your programming language of choice is, everyone is welcome!

Code Camp is an annual event here in Edmonton, organized primarily by Steven Rockarts from EDMUG. I’m really looking forward to it! Here are the details:

WHEN: Saturday, November 29th, 2008 from 9:00am until 4:30pm
WHERE: Building #5, MacEwan Downtown Campus (map)
Click here to register!

[geo_mashup_map height=”200″ width=”575″ zoom=”15″]

You should be able to see the embedded map above also – I’m testing the WP Geo plugin. Works quite well I think! I’m now testing the Geo Mashup plugin – seems to work better, and I can specify the zoom on a per-post basis!

If you’d like to present something at code camp, let us know! You can add your name to the wiki, leave a comment here, or email Steven Rockarts. Just want to attend? That’s cool too! Just register here, and then tell your friends!

We’ll have more updates as we get closer to the event, so keep an eye on the website and wiki. Hope to see you there!

My favorite hosted wiki: MindTouch Wik.is

MindTouch Wik.is Back in May I started looking for a hosted wiki for the EdmontonTweetup. I wanted a wiki so that others could contribute and help to organize our meetups. I also wanted a hosted wiki, because I didn’t want to mess around with running yet another system with yet another database. My only other requirements were that I wanted it to be free or very low cost, and relatively simple and clean (I would have been fine with some advertising).

I tried a bunch, including Wetpaint, Wikidot, PBWiki, StikiPad, Wikispaces, and finally Wik.is. I’ve had experience with both PBWiki and Wikispaces and like them both, but it was the last one that turned out to be my favorite. We’ve been using Wik.is by MindTouch to power the EdmontonTweetup wiki ever since! And today, I setup another one for Edmonton Code Camp.

Wik.is is a hosted version of Deki, the enterprise wiki solution that MindTouch sells to businesses. There are two account levels – Basic which is free, and Pro which costs $99 USD/year. The Basic level includes:

  • 100 MB of storage.
  • WYSIWYG editing.
  • The ability to have a public or private wiki.
  • Themes and the ability to edit CSS to further customize the look of the wiki.
  • Integration with popular sites like YouTube and Flickr.
  • RSS feeds, templates, redirects, and other common wiki features.

The Pro level gives you 10 GB of storage, the ability to customize the HTML, and the ability to use your own domain name.

I love that Wik.is is fast and contains no advertising! It’s simple to get started – all you need to do is choose a domain name prefix, such as “edmontoncodecamp” in http://edmontoncodecamp.wik.is. After you’re logged in you can make your wiki public, upload your own logo, and choose from one of the 20 or so pre-installed themes (or you can customize your own). You can enable anonymous editing, or require users to create an account before they can edit pages.

When I first started with Wik.is, my only complaint was that the WYSIWYG editing didn’t work in Opera or really anything other than IE and Firefox. That was fixed quite a while ago though, so I was complaint-free until today. After setting up the second wiki, I realized that there’s no such thing as a “Wik.is account”, which means I have two “mastermaq” accounts – one for the tweetup wiki and one for the code camp wiki. It would be much better if I could use just one account to login to both.

That’s a fairly minor issue though! In general I’m really happy with Wik.is, and I highly recommend it if you’re looking for a hosted wiki solution. I’m also a fan of MindTouch! They have an active blog, and a few of them are quite active on Twitter, such as the founder, Aaron Roe Fulkerson. Keep it up!

Finally, here are a few things you probably didn’t know about Deki (the software that powers Wik.is):

  • It started in July 2006 as a fork of MediaWiki (the software that powers Wikipedia)
  • The frontend is built using PHP, while the API is written in C# for Mono and the .NET Framework
  • It powers the Mozilla Developer Wiki

Windows 7 Feature Request: Presence & Status API

When RSS feeds were all the rage, Microsoft took notice and built support into Internet Explorer 7 and Windows Vista. I think the Common Feed List was a great addition to the operating system – why try to manage and synchronize a different list of feeds for each application? It makes far more sense for the OS to manage it. This situation is a good example of how Windows can make your life easier.

I would like to see a similar feature added in Windows 7 – a common presence and status API.

Presence is your availability, such as “Available”, “Busy”, and “Not Available”. There are dozens of applications that support this type of functionality in their own way. I’ve got three running right now – Windows Live Messenger, Skype, and Pidgin (well and Exchange, I suppose). You’ve probably got a similar list, perhaps with a few more applications.

Status is the short text description of what you’re doing, such as “Working in the office”. Think Twitter and Facebook. Many software applications have this type of functionality as well, including Windows Live Messenger and Skype.

Here again, the operating system should be taking care of this to make life easier. When I want to change my presence from “Available” to “Busy”, I currently have to make that change in every single application. Likewise, to update my status I need to copy and paste it to a bunch of different places. Too messy, too much work.

Here’s what I’d like to see in the API:

  • The ability to set the presence and/or status of the currently logged in user.
  • The ability to query the presence and/or status of the currently logged in user.
  • An event subscription mechanism to be notified when the currently logged in user’s presence and/or status has been updated.

That would be very cool, I think. I could then change my presence or status in Skype and it could be reflected in Windows Live Messenger and other applications. This information could also be displayed in other places, such as the Welcome screen, or in my email signature, etc.

But we can make it better – let’s hook in Windows Live support! Extend the Windows Live Presence API to support status updates as well, and let me grant access to third party services. That way I could potentially hook in Ping.fm and other services. When I update my presence and status on my computer, it updates Windows Live in the background, which in turn updates any other services I’ve added.

With that in place, this scenario becomes a reality: I open a gadget on my desktop, change my presence to “Available” and my status to “Writing a blog entry” and it’s reflected in Windows Live Messenger, Skype, Facebook, Twitter, etc.

I’d love to have that functionality! Perhaps it could work with the new location API too. I’ve got tons of feature requests for Windows 7 (as I’m sure everyone does) but this one would definitely be near the top of my wish list.

WebKit inside Internet Explorer? No thanks

webkit Inside every web browser is something called a rendering engine. The browsers get most of the glory, but it’s actually the rendering engines that do the heavy lifting. Firefox uses Gecko, Opera uses Presto, Chrome and Safari use WebKit, and Internet Explorer uses Trident. There are a few others as well, but those are the main ones. Gecko and WebKit are open source, Presto and Trident are proprietary.

Much was made of the fact that Google decided to use WebKit inside Chrome instead of building yet another rendering engine. I agree that it was the right move. Should Microsoft follow suit and replace Trident with WebKit? Steve Ballmer made some interesting comments today on the topic:

"There will still be a lot of proprietary innovation in the browser itself so we may need to have a rendering service," Ballmer said, adding, "Open source is interesting. Apple has embraced Webkit and we may look at that, but we will continue to build extensions for IE 8."

That prompted more than a few people to wish for Ballmer’s comments to come true, including Steve Hodson who said:

This idea of IE switching over to using the WebKit engine is interesting on a couple levels. First this would put two main browsers on an equal footing as far as rendering ability which would make for a much easier development cycle. It would also make for a better browsing experience for the users as developers would no longer be forced to program against the vagaries of IE.

I hear that last point all the time and it drives me nuts. Yes, Internet Explorer 6 was a nightmare to code for. But that’s simply not the case for Internet Explorer 7 or the recent Internet Explorer 8 beta. At least not in my experience.

I’d hate to see Microsoft adopt WebKit, for a few reasons:

  • Competition is good, and WebKit needs worthy competitors to continue to push the boundaries.
  • There’s nothing wrong with Trident. Why throw away something that works well and is continually improving? And I’m not just talking about the version of Trident in IE8. Microsoft has had full support for things like contentEditable since IE6, something Mozilla/Gecko still hasn’t gotten right.
  • It’s not like the existing versions of Internet Explorer would magically disappear! This would be yet another browser/rendering engine combo that developers would need to test against.

And there are good reasons that Microsoft won’t adopt WebKit too, not the least of which is licensing. Backwards compatibility is a concern also.

It might sound appealing at first, but I don’t think it would be a good thing if all the major browsers used the same rendering engine.

Windows 7 Revealed

Today at PDC, Microsoft gave the first public demonstration of Windows 7. They’ve been pretty tight-lipped about the new OS until now (with the one exception being the Engineering 7 blog), in stark contrast to the way Vista was announced. I read some of today’s reaction, and I’ve been reading the news over the last couple of weeks too. Here are a few of the things we know about Windows 7:

  • The final name will be simply Windows 7.
  • The version number will be 6.1, which indicates that the codebase is based on Vista.
  • There won’t be a major interface overhaul – just refinements and improvements to Vista’s attractive UI.
  • User Account Control (UAC) isn’t going away, but it has been refined.
  • The sidebar has been killed – gadgets now live on the desktop.
  • Windows 7 will run on netbooks on the small end, and will support up to 256 CPUs on the large end.
  • Built-in apps like Mail and Calendar are gone, with Windows Live Essentials left to fill the void.
  • The final release will likely come in the latter half of 2009.

For a simple overview of what was demonstrated today, check out The Windows Blog. If you want something a little more in-depth, check out Paul Thurrott’s SuperSite or ActiveWin. If you’re just looking for screenshots, see this post.

As you can see, it looks a lot like Vista! I’m definitely looking forward to playing with the revamped taskbar. Even ignoring the new functionality, the clear look is a welcome improvement.

Looking good so far Microsoft!

Microsoft Announcement Day 2008

windows logo Today was the first day of Microsoft’s Professional Developers Conference, but they may as well have called it official announcement day! For anyone who uses Microsoft technologies on a day-to-day basis, today is a day to remember. Definitely one for the history books of technology.

The big announcement was Windows Azure:

Today, during a keynote speech at the Microsoft Professional Developers Conference 2008 (PDC2008), Ray Ozzie, Microsoft Corp.’s chief software architect, announced Windows Azure, the cloud-based service foundation underlying its Azure Services Platform, and highlighted this platform’s role in delivering a software plus services approach to computing.

That’s a lot of marketing speak, but as usual Mary Jo Foley has a great post breaking Azure down. I’d suggest you read that to get a better idea of what exactly Azure is all about.

A few other interesting announcements:

That’s a lot of stuff for one day! As a developer, I’m a bit overwhelmed with the Azure announcement. It’s going to take a while to process. Very exciting though!

UPDATE: Colinizer has another great summary of today’s announcements on his blog. Check it out!

Windows 7 will be called…Windows 7

windows logo Microsoft announced yesterday that the next version of Windows will go by its codename when it is released, a first for the operating system. The successor to Windows Vista will be called simply, Windows 7:

Over the years, we have taken different approaches to naming Windows. We’ve used version numbers like Windows 3.11, or dates like Windows 98, or “aspirational” monikers like Windows XP or Windows Vista. And since we do not ship new versions of Windows every year, using a date did not make sense. Likewise, coming up with an all-new “aspirational” name does not do justice to what we are trying to achieve, which is to stay firmly rooted in our aspirations for Windows Vista, while evolving and refining the substantial investments in platform technology in Windows Vista into the next generation of Windows.

Even though I’m somewhat surprised by the decision, I think it’s a good one.

Most people call Windows XP just “XP” and Windows Vista just “Vista”. By the time Windows 7 comes out, it will have been ten years since we’ve had a version with a common moniker that includes the name “Windows” (of course, that would be Windows 2000). I suppose it’s possible that people may refer to it as just “Seven”, but I think “Windows 7” will be used more commonly. That’ll be good for the overall brand.

I also like the idea of evolving and refining Windows Vista, though it’s less clear how consumers will make that connection based on the name alone (I doubt most people think of Windows Vista as version 6). I think Windows 7 strikes a nice balance between “Windows Vienna” (or whatever other aspirational name was thrown around) and “Windows Vista R2”.

I wonder if this is a new trend for Microsoft? They also just released Silverlight 2 (not Silverlight 2.0). Maybe the next release of Office will be called Office 14 (they are skipping 13 due to superstition).

A version number is simple and easy-to-understand. It’s immediately clear that 7 came after 6. And removing the minor version (7.0) makes it less geeky. It also divorces the software from a yearly release cycle, which means Microsoft can focus on quality before making a new release.

I hope this decision is a sign of things to come for Windows 7. Simple and effective.

.NET Developers: Questionmark is hiring!

questionmark logo The company I work for, Questionmark, is looking to hire three developers to join our Canadian team here in Edmonton. The positions are Software Developer, Lead Software Developer, and Senior Software Developer. Here’s a bit of background on the company:

Questionmark is a company with recognised global presence in e-learning and assessment automation with software covering all aspects of this field, from authoring to delivery and reporting. Our software is used by over 3 million people in 15 different countries throughout the world. Questionmark is a fast-growing company, with a dedicated, passionate, and global workforce. We have offices in London, UK, Norwalk, CT and Tubize, Belgium. We care about the satisfaction of our employees and we reward them for meeting or exceeding expectations. The company promotes a relaxed, fun and highly productive approach to work.

I enjoy working for Questionmark! We’re an agile shop using Scrum and other things you’d expect such as unit testing and continuous integration. Another plus is that we’re not stuck in the past – we’re using .NET 3.5, ASP.NET AJAX, and lots of other new and interesting technologies. You can find more information in the job descriptions:

Job Description for Software Developer
Job Description for Lead Software Developer
Job Description for Senior Software Developer

If you’re interested in any of the positions or would like more information, either send me an email or email Kaitlyn Lardin.