Wed

Jun 18
2008

Jesse Robbins

Jesse Robbins

code_swarm - visualizing the life of open source

code_swarm was created by Michael Ogawa with Processing.

This visualization, called code_swarm, shows the history of commits in a software project. A commit happens when a developer makes changes to the code or documents and transfers them into the central project repository. Both developers and files are represented as moving elements. When a developer commits a file, it lights up and flies towards that developer. Files are colored according to their purpose, such as whether they are source code or a document. If files or developers have not been active for a while, they will fade away. A histogram at the bottom keeps a reminder of what has come before.

(thanks to Todd Ogasawara for pointing this out!)


 
Previous  |  Next

0 TrackBacks

TrackBack URL for this entry: http://blogs.oreilly.com/cgi-bin/mt/mt-t.cgi/6562

Comments: 6

  Dr Nic [06.18.08 07:13 PM]

Truly fascinating.

  My Cliparts [06.19.08 02:23 AM]

Oh wow! This looks fantastic. Very nice video!

  Roger Lancefield [06.19.08 07:37 AM]

It's particularly fascinating to see the explosion of popularity in mid-2000. Did that sudden surge of activity correspond to a particular event, or was it just a case of the project reaching critical mass, so to speak?

Any Python historians out there to enlighten those of us unfamiliar with the story?

  amk [06.19.08 08:16 AM]

The Python CVS tree was moved from an internal server to SourceForge in May 2000.

  michel rosinski [06.19.08 11:44 AM]

wow great design! Nice Idea.

  ben rigby [06.24.08 01:04 PM]

i'd like to see the *actual code* visualized as it runs. visually, showing what's sucking up the most resources, who wrote it, and what it is doing.

Post A Comment:

 (please be patient, comments may take awhile to post)






Type the characters you see in the picture above.

RECOMMENDED FOR YOU

RECENT COMMENTS