Skip to content

Commit 369bcae

Browse files
Merge pull request Code52#74 from Code52/DodoRecap
To review : Dodo Recap
2 parents 8b90469 + c3e0850 commit 369bcae

File tree

2 files changed

+62
-0
lines changed

2 files changed

+62
-0
lines changed

_posts/2012-04-16-dodo-recap.md

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
layout: post
3+
permalink: /dodo-recap.html
4+
date: 2012-04-16 23:00
5+
title: "dodo recap"
6+
author: "@shiftkey"
7+
comments: true
8+
---
9+
10+
The Code52 team had some big news over the weekend which I will address in a later post, but before we should get to the fun stuff about dodo.
11+
12+
## What's been done so far
13+
14+
This week has been about setting up a baseline and implementing core functionality.
15+
16+
At this point in time, the project is split into two distinct features:
17+
18+
- *dodo* - a Windows 8 Metro application.
19+
- *boxkite* - a library for interacting with the Twitter API in .NET 4.5 Metro.
20+
21+
## dodo
22+
23+
The application currently supports:
24+
25+
- OAuth login
26+
- Browsing the user's timeline, mentions, retweets and messages.
27+
- settings storage - persisting the user's token between sessions
28+
- diagnostics capture - so that we can log messages to the application's sandbox for debugging purposes.
29+
30+
Other functionality which as been started on but not integrated into master includes
31+
32+
- Grouping tweets by relative time ("just now", "last hour")
33+
- Semantic Zoom - collapse a group of tweets to see just the user's avatars
34+
- User Streams - rather than querying for data periodically, Twitter can stream data down to an open connection inside the app.
35+
36+
![](/img/dodo-example.png)
37+
38+
## boxkite
39+
40+
Once boxkite is feature-complete, tested and documented, it will move to a separate repository with NuGet packages available so that people can consume the API.
41+
42+
There are no immediate plans for boxkite to support other framework versions, as:
43+
44+
- it uses a number of .NET 4.5-specific features - including async/await and WebAuthenticationBroker.
45+
- there are a number of [existing libraries](https://dev.twitter.com/docs/twitter-libraries#dotnet) out there for .NET apps
46+
- I would prefer to focus on the dodo application itself in the short term.
47+
48+
If you still have the urge to check out a shiny new Twitter library, [Matt Hamilton](http://twitter.com/mabster) spent the week building a .NET 4 client called [Budgie](http://matthamilton.net/budgie) that uses the Task Parallel Library heavily.
49+
50+
## The future of dodo
51+
52+
Yes, that's a joke.
53+
54+
I'm keen to continue building this application for several reasons:
55+
56+
- many developers have been interested/curious to learn about it - while the concept of a Twitter app are familiar, being able to see the internals is where the real educational value lies.
57+
- I still have an urge to create a different experience for people to interact with Twitter. With the basics done, the next step is to focus on the UX.
58+
- There is enough lead time to have something ready for when Windows 8 ships.
59+
- There is still [a lot of work still to do](https://trello.com/board/dodo/4f82e9dfc10221fb0db2cff2).
60+
61+
And yes, others are more than welcome to get involved. Come [hang out](http://jabbr.net/#/rooms/code52).
62+

img/dodo-example.png

148 KB
Loading

0 commit comments

Comments
 (0)