Witty is a free, open source Twitter client for Windows Vista and XP powered by the Windows Presentation Foundation (WPF).
Project Name: Witty
Project site: http://code.google.com/p/wittytwitter/
Language(s): C#, WPF
License: New BSD License
Source Host: Google code
Discussion Group: WittyTwitter
Owner: Alan Le
I have a stated and known addition to Twitter. And I’ve tried a LOT of different clients for it. Check out http://twitter.pbwiki.com/Apps for a huge list of apps that are out there. I started out using SMS but that became overwhelming pretty quickly. I have used Twadget, TeleTwitter, TwittIt, Twitter-Sync (Yahoo Messenger client), Twhirl and Snitter.
It’s written in C# and WPF. It’s been a pleasure to watch it going from fairly rough to slick, stable and usable. The guys have gone back through the original and done a ton of refactoring and error handling to get it to the point that it is now.
Witty includes the following functionality: (from the project site)
- View recent Twitter statuses from the people you follow (auto-refreshing)
- View recent replies to you
- View a specific user’s timeline
- Update your twitter status
- View and respond to Direct Messages
- Links will open in the user’s default browser
Keith Elder hosts a ClickOnce installer that will keep you up to date as they continue to make updates and improvements. This is my preferred way to install it because it ensures that I’m up to date and it’s usually a very stable build. Unfortunately, the extra skins that are supposed to come with it don’t ship in the ClickOnce installer. There’s a bug in the skinning and they don’t load right. Alan Le is working on it and is refactoring the skinning to load the URI (uniform resource indicator) from an embedded resource file rather than individual files. Good advice from this article – http://msdn.microsoft.com/en-us/library/aa970069.aspx.
Licensed under the New BSD License, you are allowed to take the source and/or binaries and redistribute as long as you retain the copyright.
Feel free to jump in and discuss on the google group or