<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.5.1" -->
<rss version="0.92">
<channel>
	<title>visophyte: data made shiny</title>
	<link>http://www.visophyte.org/blog</link>
	<description>visualizing things with python</description>
	<lastBuildDate>Wed, 09 Jul 2008 01:14:49 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>gloda&#8217;s first (primitive) visualization</title>
		<description>

A primitive visualization augments the gloda "other messages by author" listing by showing the messages sent by the author over time.  Messages are stacked by day.  The currently selected message is in darkest blue and also very wide.  Other messages from the same thread/conversation are in lighter blue and less ...</description>
		<link>http://www.visophyte.org/blog/2008/07/08/glodas-first-primitive-visualization/</link>
			</item>
	<item>
		<title>gloda milestone 1</title>
		<description>

I am declaring milestone 1 of gloda (the global database extension for Thunderbird 3.x) / expmess (the experimental message view extension for Thunderbird 3.x) reached.  Milestone 1 basically consists of:

	It statically indexes all of your folders.  It does not track changes made to your mailboxes.  It will become confused and ...</description>
		<link>http://www.visophyte.org/blog/2008/07/07/gloda-milestone-1/</link>
			</item>
	<item>
		<title>thunderbird global database m1-ish</title>
		<description>The 'gloda' (global database) and 'expmess' (experimental message view) Thunderbird extensions are nearly to milestone 1...



The screenshot scenario is that we have 2 months of apache-dev archives in two separate folders, July and August.  We have a message selected in the month of July, yet the 'data mine' to the ...</description>
		<link>http://www.visophyte.org/blog/2008/07/05/thunderbird-global-database-m1-ish/</link>
			</item>
	<item>
		<title>Someone created a Thread Arc vis for Thunderbird!</title>
		<description>Alexander C. Hubmann-Haidvogel has created a Thread Arc visualization extension for Thunderbird!  Get info on the extension with some pretty pictures or just go straight for the extension at AMO.  Thanks to David Ascher for the heads up. </description>
		<link>http://www.visophyte.org/blog/2008/05/27/someone-created-a-thread-arc-vis-for-thunderbird/</link>
			</item>
	<item>
		<title>pecobro, the tell-you-who-reads/writes-what performance code browser</title>
		<description>No cool pictures, but I've enhanced and exposed the global reader/writer understanding of javascript code.  In other words, pecobro now does a passable job at telling you what global variables a given javascript file reads from/writes to, and who else writes to/reads from those variables.  False negatives are expected (don't ...</description>
		<link>http://www.visophyte.org/blog/2008/05/20/pecobro-the-tell-you-who-readswrites-what-performance-code-browser/</link>
			</item>
	<item>
		<title>master control pecobro, the overkill performance code browser</title>
		<description>

The title isn't true yet, but it's disturbingly almost-true.  Pecobro's hackish underpinnings have been "accidentally" replaced with surprisingly forward-looking code capable of supporting a much fancier feature set.  (I didn't mean to, but I got tricked because the incremental cost to doing the 'right thing' was always so low.)

The trace ...</description>
		<link>http://www.visophyte.org/blog/2008/05/03/master-control-pecobro-the-overkill-performance-code-browser/</link>
			</item>
	<item>
		<title>pecobro: the performance code browser (early stage)</title>
		<description>

At the beginning of last week, I had gotten dtrace working on a Mac Mini using the Mozilla javascript-provider probes.  Very cool stuff, but it left me with several questions about what would really be best to do next:

	How do I best understand what I'm seeing?  (Most of the codebase ...</description>
		<link>http://www.visophyte.org/blog/2008/04/08/pecobro-the-performance-code-browser-early-stage/</link>
			</item>
	<item>
		<title>Mozilla JavaScript DTrace Probes, visichron style</title>
		<description> 

This visualization is the result of an adapted visichron.py script (from my chronicle-recorder 'chroniquery' bindings) run against the output of a custom DTrace script (using the Mozilla JS providers) on OS X.  It's a proof-of-possibility rather than anything immediately useful.

The differences from the last visichron post (using chronicle-recorder as a ...</description>
		<link>http://www.visophyte.org/blog/2008/03/31/mozilla-javascript-dtrace-probes-visichron-style/</link>
			</item>
	<item>
		<title>status/future fyi. no pictures.</title>
		<description>I have accepted a position at Mozilla Messaging and will start at the end of March.  Posting has been rare as of late and will be rare until then because my spare cycles are being given over to providing closure to my day-job projects, dealing with various hardware failures, ...</description>
		<link>http://www.visophyte.org/blog/2008/03/09/statusfuture-fyi-no-pictures/</link>
			</item>
	<item>
		<title>chronicle-recorder and amd64, hooray!</title>
		<description> 

My personal laptop rolls amd64-style (rather than i686), and chronicle-recorder's valgrind component was not working on it ("illegal instruction").  I have done some vendor-branch dancing to get chronicle-recorder's valgrind sub-directory to use valgrind 3.3.0.  A bzr branch of just the valgrind subdirectory (drop-in or build separately and ...</description>
		<link>http://www.visophyte.org/blog/2008/01/27/chronicle-recorder-and-amd64-hooray/</link>
			</item>
</channel>
</rss>
