[Design] Twitter in Chandler?

[Mimi Yin]

Morgen demo'd a Twitter parcel at the staff meeting today (sorry to  
steal your thunder Morgen) which set off all kinds of flammables in  
my head.

In our interview with Robert Scoble, Scoble spoke about sitting in  
Chandler and swimming in a sea of twitters, feeds, news tickers etc.  
Morgen took the first steps towards realizing that vision. I'm  
picking up where he left off with a sketchy mock-up of what the user  
experience might be like. See wiki page for screenshot.

http://chandlerproject.org/Notes/TwitterHalfbaked
Note This is not only a proposal for a Twitter extension, but is  
intended to provide space in the UI for ambient information, as in  
information people soak up, stuff that doesn't necessarily require  
your full attention, but instead floats around you like elevator  
music. Different people will define *ambient* in different ways. The  
design list is at the core of of the work I do, but is probably  
ambient information for most list subscribers. Examples of sources of  
*ambient* information include: Twitter, Facebook status, News  
tickers, RSS feeds, mailing lists, etc.

+ Floating palette where all the twits come in

+ It'd be nice if it weren't just twits, but feeds of all shapes and  
sizes (in the fullness of time as we like to say)

+ A drop-down at the top where I can choose to either:
- View all feeds (I know feeds is the wrong word, but don't have a  
better one right now.)
- View a single feed
- Add a feed

+ Twits / feed things scroll by, not sure if we need to archive these  
things? We would need separate UI for that.

+ If one of the ambient items is just a headline for a longer blog  
post / article, then clicking on it will take you to the article in a  
browser.

+ At the bottom is an entry box to submit your own twit.

Now here's the killer feature:
+ Drag and drop individual twits into the main Chandler window so you  
can stamp it as a task, add it to the calendar etc.
+ I imagine that some feeds actually contain valid .ics files, so  
those should get parsed as events automagically, if dragged into the  
main window.
Things to Consider

+ Do we want to have a twit/feed palette per collection?
+ Do we want to give users a way to specify where they'd like to send  
their twit? Twitter v. Pounce v. Facebook v. MySpace?, etc.
+ Haven't figured out a way to integrate the 'timeline/calendar' view  
that Morgen demo'd. But it was a very cool way to browse one's  
twitter archive.

Mimi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20071018/dbc56ff8/attachment.html