Arial vs Clear Sans

This is Clear Sans - released in late 2013 by the Intel Open Source Technology Center Overal. It looks like a slightly more contemporary, humanist version of Arial. Overall, we can't see too much to get excited over. Do note that it comes with a very thin variant that Arial lacks.



PDF of the comparison is here:

Glyph comparisons (Arial in blue, Clear Sans in red)






Content-Adaptive Image Downscaling from Microsoft Research  

Recently revived on a reddit discussion, it's good to see that we can still do better at image downsampling –  an often neglected responsibility –  to which the ubiquity of bad thumbnail images on the web can attest.

Link to paper:

Some samples from the paper:










Generating Auto-Incremented Version numbers with PowerShell

The code snippet below is something I had to write to simplify some build & deployment. Instead of me having to remember the latest version number to use, this PowerShell snippet lets me store the current version number as a Major.Minor.Patch (for example 1.2.3) one-line text file. The script updates the version number every time it is run.

Some techniques demonstrated:

  • Simple reading and writing of strings with Text files
  • Converting Strings to Integers and back
  • Splitting a string


Write-Host Calculate new version number

$curverfilename= "d:\curver.txt"

$curver = Get-Content $curverfilename | Out-String

Write-Host Current Version $curver

$tokens = $curver.Split(".")

$major = [int]( $tokens[0])

$minor = [int]( $tokens[1])

$patch = [int]( $tokens[2])

$new_patch = $patch + 1

$Version = ([string] $major)+"."+ ([string] $minor ) +"." + ([string]$new_patch)

Write-Host $Version

$Version | Out-File $curverfilename


Interlude: Swan Lake through Zeno Music Visualizer

Let’s start 2014 with something inspiring.

Swan Lake - Zeno Music Visualiser from Glenn Marshall on Vimeo.


On the future of MetaWeblogSharp

There is a good change coming.

MetaWeblogSharp is merging into the MetaWeblog.Portable project (

Benefits for You

  • The code will see more active development and will as a result be more reliable with different MetaWeblog services.
  • The “Portable” part means that you’ll be able to use the code on .NET Framework 4.5, Windows 8, Windows 8 RT, Windows Phone 8, iOS, and Android! MetaWeblogSharp only ever supported Windows 8. As a developer who wants people to use his code – this naturally makes me very happy.
  • It will have great support for asynchronous operations – MetaWeblogSharp only supported synchronous use
  • It doesn’t fracture the codebase and in turn benefits the greatest number of developers.

Key Points

  • I realize a few of you are still using MetaWeblogSharp. The project will not suddenly disappear right now. I’ll keep the project on CodePlex and the binaries on NuGet for at least the next six months
  • MetaWeblogSharp is now in maintenance mode. If you find an bug or have a question feel free to contact me. I’ll make selected bugfixes into MetaWeblogSharp and port them into MetaWeblog.Portable.
  • If you have a new feature request, likely this will go directly MetaWeblog.Portable. (Though I would consider adding it to MetaWeblogSharp if it is incredibly important)

Next Steps

  • Currently, I’m working on the MetaWeblog.Portable project on GitHub. My current focus is to make general compatibility improvements and more important add a framework for testing the MetaWeblog.Portable client.
  • As part enabling unit testing, I’m building a very simple MetaWeblog Server component – a simple HTTP server that implements a xml/filesystem based blogging system. A side-benefit of this simple MetaWeblog-based blogging client is that if you ever want to build your own toy web server or XmlRPC server or MetaWeblog server you will have a modern, clean example of how to do it.


Thanks for everyone who has used MetaWeblogSharp and remember with this change you’ll get more features – not less.