{"id":990,"date":"2007-05-31T09:31:15","date_gmt":"2007-05-31T09:31:15","guid":{"rendered":"\/ifbookblog\/?p=990"},"modified":"2007-05-31T09:31:15","modified_gmt":"2007-05-31T09:31:15","slug":"time_machine","status":"publish","type":"post","link":"https:\/\/futureofthebook.org\/blog\/2007\/05\/31\/time_machine\/","title":{"rendered":"time machine"},"content":{"rendered":"<p>The other day, a bunch of us were looking at this <a href=\"http:\/\/www.apple.com\/macosx\/leopard\/timemachine.html\">new feature<\/a> promised for Leopard, the next iteration of the Mac operating system, and thinking about it as a possible interface for document versioning.<br \/>\n<object width=\"425\" height=\"350\"><param name=\"movie\" value=\"http:\/\/www.youtube.com\/v\/nWdkfCwd4qU\"><\/param><param name=\"wmode\" value=\"transparent\"><\/param><embed src=\"http:\/\/www.youtube.com\/v\/nWdkfCwd4qU\" type=\"application\/x-shockwave-flash\" wmode=\"transparent\" width=\"425\" height=\"350\"><\/embed><\/object><br \/>\nI&#8217;ve yet to find something that does this well. Wikis and and Google Docs give you chronological version lists. In Microsoft Word, &#8220;track changes&#8221; integrates editing history within the surface of the text, but it&#8217;s ugly and clunky. Wikipedia has a version comparison feature, which is nice, but it&#8217;s only really useful for scrutinizing two specific passages.<br \/>\nIf a document could be seen to have layers, perhaps in a similar fashion to Apple&#8217;s Time Machine, or more like <a href=\"\/mckenziewark\/gamertheory2.0\">Gamer Theory<\/a>&#8216;s stacks of cards, it would immediately give the reader or writer a visual sense of how far back the text&#8217;s history goes &#8211; not so much a 3-D interface as 2.5-D. Sifting through the layers would need to be easy and tactile. You&#8217;d want ways to mark, annotate or reference specific versions, to highlight or suppress areas where text has been altered, to pull sections into a comparison view. Perhaps there could be a &#8220;fade&#8221; option for toggling between versions, slowing down the transition so you could see precisely where the text becomes liquid, the page in effect becoming a semi-transparent membrane between two versions. Or &#8220;heat maps&#8221; that highlight, through hot and cool hues, the more contested or agonized-over sections of the text (as in the Free Software Foundations <a href=\"http:\/\/gplv3.fsf.org\/comments\/gplv3-draft-2.html\">commentable drafts of the GNU General Public License<\/a>).<br \/>\nAnd of course you&#8217;d need to figure out comments. When the text is a moving target, which comments stay anchored to a specific version, and which ones get carried with you further through the process? What do you bring with you and what do you leave behind?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The other day, a bunch of us were looking at this new feature promised for Leopard, the next iteration of the Mac operating system, and thinking about it as a possible interface for document versioning. I&#8217;ve yet to find something that does this well. Wikis and and Google Docs give you chronological version lists. In [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[76,467,891,1861,1952,2011,2042],"tags":[2997],"class_list":["post-990","post","type-post","status-publish","format-standard","hentry","category-apple","category-design","category-interface","category-the_networked_book","category-versioning","category-wiki","category-writing","tag-versioning-writing-interface-design-wiki-apple-the_networked_book"],"_links":{"self":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/990","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/comments?post=990"}],"version-history":[{"count":0,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/990\/revisions"}],"wp:attachment":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/media?parent=990"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/categories?post=990"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/tags?post=990"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}