The Eric Wroolie Blog

Overpass Experiences

  • Blog
  • Videos
  • Overpass Apps

Powered by Overpass Apps

WPF and XAML

October 13, 2006 by wroolie Leave a Comment

So I wrote yesterday a little bit about how difficult designing a GUI can be for a developer. We deliver the world of functionality, but get nagged about the font style. I once argued for hours with a business user whether a certain function should have been launched with a button or a hyperlink.

With Windows Vista, Microsoft will be releasing the Windows Presentation Foundation classes. These will be in Vista by default, but can also be installed on XP. WPF will be one quarter of the release being billed as “.Net 3.0” (although you will find much debate on the web as to whether or not it deserves the label–it’s not really a new version of .Net).

WPF will add a new layer to Windows presentation. A new XML protocol called XAML (pronounced Zammel) will allow developers or designers to design GUI’s with a markup language similar to HTML.

If I want a button that says Click Me, the XAML would look like this:

<Button HorizontalAlignment=”Left” Margin=”122,194,0,228″ Width=”116″ x:Name=”btmMyButtonName” Content=”Click Me!”/>

By separating out the design from development, actual I’ve-been-to-art-school designers can develop GUI’s and developers can build robust systems.

If this was all that XAML could do, there would be a huge ‘so what’ factor, but the advances in GUI design are pretty spectacular.

One of the things that really used to bother me in the VB6 days was that every application we’d ever build would look that same. It was a square box with other square boxes on it. A lot of the time it was gray. We used to argue about whether to keep the system colours (and allow users to adjust the look of the form with their desktop theme) or jazz it up with some bitmaps and change the background color. Nothing we’d design would ever look like a cool app from the movies (Like, when someone gets an email in the movies, a giant envelope flies around the screen and opens up in front of them). Our apps were boring. .Net apps are that big an improvement. Although you can inherit the Form class and make a round form or something, it was more trouble than it was worth.

With XAML, the designer starts with a blank page and builds a GUI from thin air. He or she can easily change the appearance of all buttons, forms, listboxes, etc.

For designers, this would be as easy as drawing pictures on a palette.

Microsoft is releasing a suite of tools called Microsoft Expression. The three tools in this suite include Graphic Designer, Interactive, and Web Developer.

The Microsoft Expressions Graphic Designer application is basically a paint programme like Photoshop or PaintShopPro. The only difference is that it will export Vector graphics in XAML format which can easily be loaded into Expressions Interactive.Interactive Designer

Expressions Interactive Designer is an application that allows the designer to build GUI’s with a WYSIWYG editor. This produces the XAML–including mouseovers, button clicks, etc.

The third tool in the suite, “Web Designer”, is used for Web applications. (obviously).

I’ve always prided myself on being an HTML guy. I don’t do WYSIWYG. I’ve never trusted WYSIWYG-generated code to render consistently in all browsers. However, I think I will go the Expressions route when building XAML. Since we are talking single platform–single runtime– I see no reason not to use it.

I’ll save a post for Microsoft Expressions for another time. If you want to see Microsoft’s official Expressions website, click here. I’ve downloaded RC1 of the software and don’t have any problems with it so far.

Filed Under: C# Coding, Software Dev & Productivity

The Trials of GUI Design

October 12, 2006 by wroolie Leave a Comment

I’m a sucker for GUI design.

I know a lot of developers (especially non-Microsoft developers) who consider GUI design to be the worst part of a software project. It’s not difficult to see why. Imagine spending months working on a project–making sure everything works the way it should. You make sure that users can’t enter any illegal data, the application fails gracefully in a server outage, and it can hold the maximum amount of users. You also design the GUI so it is the most logical and user-friendly features.

What do UAT testers say to your Herculean efforts?

“I don’t like the font.”

They don’t like the font.

A two-minute afterthought on your part (“Should I use Arial or Times New Roman?”) and that is what they pick up on. “Yeah,” you recover, “but just go ahead and try to break the system. This thing is water-tight, baby!”

“Can’t we just change the font first?”

It is soul destroying, let me tell you.

I personally like GUI design, despite the criticism. Nothing feels better in a project than having the creative freedom to improve the user experience. When deprived of the freedom, it drives me crazy.

When I was at BBC, the development projects were divided into Designers and Developers (I was on the developer team). Designers would whip out cool looking graphics and html using Photoshop and Dreamweaver on their Macs (without having a clue as to how the application works in the background) and send the html and graphics to developers to add the plumbing.

For web applications, this division of developer and designer worked fine (well, it worked okay), but for desktop applications this was not really possible. Aside from sending screenshots to developers, there was little that could be done besides a developer trying to mimic the screenshot in the GUI (“You got the font wrong.”).

But now that all looks set to change with WPF in .Net 3. WPF, or Windows Presentation Foundation, is a set of libraries allowing an application present its GUI using a markup language with .Net 2 code facilitating the plumbing. Designers can use the Microsoft Expressions suite (a WYSIWYG XAML editor) to produce a GUI that developer can attach to their applications. Better yet, rather than waiting for designers to deliver the goods, developers and designers can work on the same project concurrently.

This post is going longer than I intended it to, so I will write more tomorrow about this. I’ve spent the last few days playing with XAML and Expressions Interactive Designer and am convinced that the era of GUI design is going to change quite a bit in the next few years.

Filed Under: Software Dev & Productivity

Nike+ Sensor for the Ipod Nano

October 9, 2006 by wroolie 2 Comments

When I left BNP Paribas, my wonderful colleagues bought me an IPOD Nano. This is something I never would have bought for myself, so it was perfect. I love it and run with it all the time.

This week, I tried out the new Nike+ Ipod sensor this week. This cool little gadget tracks your runs and allows you to listen to music at the same time.

A couple of months ago, Apple and Nike teamed up to produce the Nike+ running music system. This includes the IPOD Nano (which is perfect for running since it uses flash memory instead of a hard drive), a special receiver which attaches to the base of the Ipod and a small sensor which sits in the sole of a special Nike+ shoe.

ImageThe sensor in the shoe is picked up by the receiver in the Ipod and tracks your distance, calories burned, current speed, etc. By touching the centre button of the Ipod while running, you get a male of female voice give you a status report (ie. “Twenty-three minutes. Distance: 2.43 miles. Current Speed: 7:13 minutes per mile.” When you sync up your Ipod with iTunes at the end of your run, your workout details are uploaded to a secure page on the Nike website which tracks your running history, speed, etc. You can also, they say, challenge someone else to a distance race on the other side of the world.

This technology has been around for about a month or so. The sensor kit itself only costs about £20, which is not too steep if you already have the Nano. The real cost is the special Nike+ shoe that is “required” to use the kit. This little gadget ensures you are stuck with Ipod and Nike for the rest of your life.

However, after doing some web research, I found articles detailing how to use the sensor with Non-Nike+ shoes. It involves putting some Velcro on the tongue of your shoe and the the sensor and placing it under your laces. I’ve done that to my Nike (but non-Nike+) shoes. It worked great. The distance reported was very accurate and I found it alarming how slow my running speed was at times. For the base sensor kit, I got all the bells and whistles without the expensive shoes.

If you’ve found this post because you want to know if the velcro method of attaching the sensor works or not, I can attest that it does. It works very well. Now, I’m listening to music or audio books and keeping track of my miles accumulated.

I highly recommend the Nike+ Ipod sensor (but not the shoes).

You can buy the sensor from Apple Store. http://store.apple.com

Filed Under: Miscellaneous Rants

  • « Previous Page
  • 1
  • …
  • 97
  • 98
  • 99
  • 100
  • 101
  • …
  • 111
  • Next Page »

Recent Posts

  • My Gig and the Imposter Syndrome
  • Getting Picked Last for Teams in PE
  • One Little Growth Opportunity at a Time
  • I’m sorry if I look like I know what I’m doing
  • New Years Reclamations