<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>REBECCA E SPITZER &#187; tangible user interface</title>
	<atom:link href="http://www.rebecca-e-spitzer.com/blog/tag/tangible-user-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rebecca-e-spitzer.com/blog</link>
	<description>combining design, journalism, and technology. when i feel like it, anyways.</description>
	<lastBuildDate>Tue, 09 Mar 2010 23:18:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Dynamic Rehearsal Presentation Post-Mortem</title>
		<link>http://www.rebecca-e-spitzer.com/blog/2009/12/dynamic-rehearsal-presentation-post-mortem/</link>
		<comments>http://www.rebecca-e-spitzer.com/blog/2009/12/dynamic-rehearsal-presentation-post-mortem/#comments</comments>
		<pubDate>Wed, 16 Dec 2009 05:04:23 +0000</pubDate>
		<dc:creator>Rebecca</dc:creator>
				<category><![CDATA[TUI]]></category>
		<category><![CDATA[dynamic rehearsal]]></category>
		<category><![CDATA[tangible user interface]]></category>
		<category><![CDATA[vimeo]]></category>

		<guid isPermaLink="false">http://www.rebecca-e-spitzer.com/blog/?p=178</guid>
		<description><![CDATA[Well, our presentation went out without much of a hitch last week; we weren&#8217;t completely pleased with how much we were able to explain, because the implementation of the project can get confusing and we got caught up in the details without giving a lot of the big picture. We did play the video first, [...]]]></description>
			<content:encoded><![CDATA[<p><span class="drop">W</span>ell, our presentation went out without much of a hitch last week; we weren&#8217;t completely pleased with how much we were able to explain, because the implementation of the project can get confusing and we got caught up in the details without giving a lot of the big picture. We did play the video first, so hopefully that did a lot of the explaining. Here&#8217;s the video (though not the final form, probably):</p>
<p><object width="400" height="300"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=8126974&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=8126974&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="300"></embed></object>
<p><a href="http://vimeo.com/8126974">Dynamic Rehearsal Project</a> from <a href="http://vimeo.com/user2786230">Rebecca Spitzer</a> on <a href="http://vimeo.com">Vimeo</a>.</p>
<p>We did get a lot of great feedback, though, so that was really rewarding! I&#8217;m pleased with how much we got done, and it seems so was everyone else. </p>
<p>We&#8217;re spending this week wrapping everything up, making a display website and commenting up our code files. What a crazy couple of weeks!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rebecca-e-spitzer.com/blog/2009/12/dynamic-rehearsal-presentation-post-mortem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Functional Dynamic Rehearsal Prototype</title>
		<link>http://www.rebecca-e-spitzer.com/blog/2009/12/functional-dynamic-rehearsal-prototype/</link>
		<comments>http://www.rebecca-e-spitzer.com/blog/2009/12/functional-dynamic-rehearsal-prototype/#comments</comments>
		<pubDate>Tue, 01 Dec 2009 21:12:06 +0000</pubDate>
		<dc:creator>Rebecca</dc:creator>
				<category><![CDATA[TUI]]></category>
		<category><![CDATA[dynamic rehearsal]]></category>
		<category><![CDATA[prototype]]></category>
		<category><![CDATA[tangible user interface]]></category>

		<guid isPermaLink="false">http://www.rebecca-e-spitzer.com/blog/?p=154</guid>
		<description><![CDATA[Over the last two weeks, our project group has been working to implement a preliminary version of our Dynamic Rehearsal project, spending days and nights programming in C# on the Microsoft Surface Simulator. Our goals were to implement high fidelity look to the project and a medium-low fidelity interaction model, and we made it part [...]]]></description>
			<content:encoded><![CDATA[<p><span class="drop">O</span>ver the last two weeks, our project group has been working to implement a preliminary version of our Dynamic Rehearsal project, spending days and nights programming in C# on the Microsoft Surface Simulator. Our goals were to implement high fidelity look to the project and a medium-low fidelity interaction model, and we made it part of the way there.</p>
<p>Because so much of the interface involves dynamically generating elements of the interface based on who is logged in to the system and what data is most recent, we decided to start with a one of the most basic and difficult elements of the interface: the timeline. For every rehearsal displayed by the interface, there is a timeline generated to display which actors are onstage at particular times, as well as where notes were taken on their performances. To work with this, we started from scratch, building a number of original classes (ie: &#8220;Rehearsal&#8221;, &#8220;Person&#8221;, &#8220;Timeline&#8221;, &#8220;Note&#8221; objects, etc) and then writing methods to dynamically generate an image.</p>
<p>The second aspect of the interface we chose to implements was the parsing of notes files. We have a computerized pen that will record the notes a director takes, and we need to be able to import that information into our program, creating new Note objects and assigning them to the right people and timestamps. Though the notes do not display at this point, we have been able to parse them in &#8211; very exciting.</p>
<p>Personally, I focused most on the design of the interface of the project, which has been one of the more disastrous aspects of this milestone. Without any data to work with, I drew up a basic interface; it was difficult, however, to visualize how it would look with an actual timeline, video, and notes. It wasn&#8217;t until last night (well, morning, really) that we finally returned from Thanksgiving break to integrate our work together, and at that point we realized we were working with a terribly ugly and confusing interface. (I think we started calling it &#8220;the ugliest interface we&#8217;ve ever made,&#8221; actually.) Currently, it looks like this in the simulator:</p>
<p><a href="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/12/dynamic-rehearsal.jpg"><img class="alignnone size-full wp-image-155" title="dynamic-rehearsal" src="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/12/dynamic-rehearsal.jpg" alt="dynamic-rehearsal" width="400" height="333" /></a></p>
<p>(We&#8217;re not sure where that grey border at the bottom is from, why the interface doesn&#8217;t fit on the screen, or why some notes are black. Debugging will be fun!)</p>
<p>So! For the next deadline, we&#8217;ve decided to overhaul the interface. One of the biggest hurdles to get past is making our interaction workspaces show up in ScatterView panels, which are able to be moved around the Surface with gestural interaction. I will be reorganizing this main interaction space into a smaller ScatterView panel, as well as designing a smaller &#8220;Recent Notes&#8221; panel and a singular &#8220;Note&#8221; panel so that users can pull a note from the list to view individually. Hopefully, this will make the application easier to use, more collaborative, and more aesthetically pleasing. Everything needs to be resdesigned before we can continue to program interactions though, so we&#8217;ll be jumping in to the design tonight. We&#8217;ll also be filming a rehearsal tonight (of the show I&#8217;m working on, <em>Gibraltar</em>, which opens Thursday) so that we can have some accurate, useful source material for our final presentation.</p>
<p>Overall, the programming and design of the project have both been difficult; I think every member of our team is struggling at every turn. We have made huge amounts of progress since our paper prototype, though, so I have hope that we will be able to both fix the problems we&#8217;re facing and continue to implement more interactivity. I&#8217;m excited to see how the next two weeks go, and I&#8217;m also excited to see more progress on the projects other groups are working on, for everyone&#8217;s presentations on their functional prototypes were great!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rebecca-e-spitzer.com/blog/2009/12/functional-dynamic-rehearsal-prototype/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dynamic Rehearsal Project Update</title>
		<link>http://www.rebecca-e-spitzer.com/blog/2009/11/dynamic-rehearsal-project-update/</link>
		<comments>http://www.rebecca-e-spitzer.com/blog/2009/11/dynamic-rehearsal-project-update/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 15:31:27 +0000</pubDate>
		<dc:creator>Rebecca</dc:creator>
				<category><![CDATA[TUI]]></category>
		<category><![CDATA[tangible user interface]]></category>
		<category><![CDATA[theater]]></category>

		<guid isPermaLink="false">http://www.rebecca-e-spitzer.com/blog/?p=143</guid>
		<description><![CDATA[For the next phase of our tangible user interface project, I drew up the following use scenario:
Ousystem is created for the general use of a theatrical production team: director, cast, and crew. A typical user has extensive experience in theatre, but not with computers. With the assistance of our system, they will be able to [...]]]></description>
			<content:encoded><![CDATA[<p><span class="drop">F</span>or the next phase of our tangible user interface project, I drew up the following use scenario:</p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">Ousystem is created for the general use of a theatrical production team: director, cast, and crew. A typical user has extensive experience in theatre, but not with computers. With the assistance of our system, they will be able to enjoy the benefits of computer-assisted analysis, review, and documentation of rehearsals without a basis of knowledge about computers or programming. </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;"> </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">The system will record the rehearsal process with video, audio, location information, and text. Video and audio will be provided by an installed video camera, location information will be provided by RFID tags worn by actors, and text will be automatically sourced from notes being taken by the director, stage manager, and other members of the production staff. With computerized pens, we will be able to digitally record the notes being taken by these users. All interactions take place within the theater space. </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;"> </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">The interaction with our system is primarily with the Microsoft Surface. The video camera will be linked to the Surface, automatically recording when the Surface application is activated in Rehearsal mode. Actors only need to wear their RFID tags when they are onstage (to record at what points they enter and exit the stage space) and production staff members only need to write with computerized pens, which electronically record, convert and transfer their notes to the Surface. All other interaction is with the Surface. </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">At any point, any user can log into the Microsoft Surface application tailored to their production, which will store and sort the data recorded during rehearsals. Upon logging in, a user is provided with a tailored selection of recent rehearsals. For the most common user, an actor in the production, the Surface application would provide a number of workspaces: an area within which video and notes from the most recent rehearsal could be reviewed, an area within which the most recent unread notes for the actor could be reviewed, and thumbnails with which older rehearsals and notes could be accessed. With these workspaces, a user is able to both review their performance and quickly see which areas of the production need further work. </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;"> </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">To begin a user&#8217;s interaction with the Surface, they only need to place their hand on the surface to bring up their workspaces: recent rehearsal, recent notes, and thumbnails. Once these spaces are open, they can be moved around the surface and resized as necessary. A user can replay video, shuffle through notes, mark notes as read, and compare rehearsals to review their progress. Within the main workspace, there are three main elements. At the top of the space is a global timeline of the entire rehearsal. The times in which the given actor was onstage are noted on the timeline with a color-coded bar, as are all notes for the actor. On the left side space is the video display and an expanded timeline, showing a more specific portion of the rehearsal. The section highlighted in the expanded timeline is noted with brackets; identical brackets also appear on the global timeline. The expanded timeline can be pushed to the left or right to move to a different point in the video. On the right side of the screen is a list of notes relevant to the highlighted portion of the rehearsal and to the current user. Each note is displayed with markers to show what type of note it is and which user it pertains to. Notes can be marked as read or unread, and notes that the user is finished with can be discarded. The full list of notes is also scrollable at the top and bottom. Notes in the panel are also sortable by character or type by selecting the tabs to the right side of the panel. This notes panel can be collapsed into the workspace if the user is solely interested in the video. </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;"> </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">The system can also be user collaboratively, with multiple users. To join the review process, a second users needs only to place their hand on the surface, which will add their profiles to existing workspaces. The most recent shared rehearsal will occupy the recent rehearsal space, and any recent unread notes targeted to both users will appear in the recent notes space. Together, multiple users can watch video, discuss notes, and review their progress. In expanded rehearsal panels, information about all active users are displayed: on the global and expanded timelines, the appearances of all users are denoted with extra bars and in the notes panel, only notes pertinent to all active users are displayed. Information about a certain actor can be deactivated by selecting the appropriate tabs to the right side of the notes panel. Multiple users may choose to open more than one expanded rehearsal workspace to compare videos. </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;"> </div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">With this system, a theatrical production team gains the ability to record, analyze, and review their progress without having to alter their usual rehearsal routine. Information in the form of video, audio, location, and text is put together to provide a comprehensive record of the rehearsal process. The system will aid in the review process and facilitate a more collaborative approach.</div>
<p> </p>
<p>Our system is created for the general use of a theatrical production team: director, cast, and crew. A typical user has extensive experience in theatre, but not with computers. With the assistance of our system, they will be able to enjoy the benefits of computer-assisted analysis, review, and documentation of rehearsals without a basis of knowledge about computers or programming. </p>
<p>The system will record the rehearsal process with video, audio, location information, and text. Video and audio will be provided by an installed video camera, location information will be provided by RFID tags worn by actors, and text will be automatically sourced from notes being taken by the director, stage manager, and other members of the production staff. With computerized pens, we will be able to digitally record the notes being taken by these users. All interactions take place within the theater space. </p>
<p>The interaction with our system is primarily with the Microsoft Surface. The video camera will be linked to the Surface, automatically recording when the Surface application is activated in Rehearsal mode. Actors only need to wear their RFID tags when they are onstage (to record at what points they enter and exit the stage space) and production staff members only need to write with computerized pens, which electronically record, convert and transfer their notes to the Surface. All other interaction is with the Surface. </p>
<p>At any point, any user can log into the Microsoft Surface application tailored to their production, which will store and sort the data recorded during rehearsals. Upon logging in, a user is provided with a tailored selection of recent rehearsals. For the most common user, an actor in the production, the Surface application would provide a number of workspaces: an area within which video and notes from the most recent rehearsal could be reviewed, an area within which the most recent unread notes for the actor could be reviewed, and thumbnails with which older rehearsals and notes could be accessed. With these workspaces, a user is able to both review their performance and quickly see which areas of the production need further work. </p>
<p>To begin a user&#8217;s interaction with the Surface, they only need to place their hand on the surface to bring up their workspaces: recent rehearsal, recent notes, and thumbnails. Once these spaces are open, they can be moved around the surface and resized as necessary. A user can replay video, shuffle through notes, mark notes as read, and compare rehearsals to review their progress. Within the main workspace, there are three main elements. At the top of the space is a global timeline of the entire rehearsal. The times in which the given actor was onstage are noted on the timeline with a color-coded bar, as are all notes for the actor. On the left side space is the video display and an expanded timeline, showing a more specific portion of the rehearsal. The section highlighted in the expanded timeline is noted with brackets; identical brackets also appear on the global timeline. The expanded timeline can be pushed to the left or right to move to a different point in the video. On the right side of the screen is a list of notes relevant to the highlighted portion of the rehearsal and to the current user. Each note is displayed with markers to show what type of note it is and which user it pertains to. Notes can be marked as read or unread, and notes that the user is finished with can be discarded. The full list of notes is also scrollable at the top and bottom. Notes in the panel are also sortable by character or type by selecting the tabs to the right side of the panel. This notes panel can be collapsed into the workspace if the user is solely interested in the video. </p>
<p>The system can also be user collaboratively, with multiple users. To join the review process, a second users needs only to place their hand on the surface, which will add their profiles to existing workspaces. The most recent shared rehearsal will occupy the recent rehearsal space, and any recent unread notes targeted to both users will appear in the recent notes space. Together, multiple users can watch video, discuss notes, and review their progress. In expanded rehearsal panels, information about all active users are displayed: on the global and expanded timelines, the appearances of all users are denoted with extra bars and in the notes panel, only notes pertinent to all active users are displayed. Information about a certain actor can be deactivated by selecting the appropriate tabs to the right side of the notes panel. Multiple users may choose to open more than one expanded rehearsal workspace to compare videos. </p>
<p>With this system, a theatrical production team gains the ability to record, analyze, and review their progress without having to alter their usual rehearsal routine. Information in the form of video, audio, location, and text is put together to provide a comprehensive record of the rehearsal process. The system will aid in the review process and facilitate a more collaborative approach.</p>
<p> </p>
<p> </p>
<p>Our team also worked to put together the following storyboard elements, though recent conversations have led to some basic changes.</p>
<p><a href="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0425.JPG"><img class="alignnone size-medium wp-image-146" title="IMG_0425" src="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0425-225x300.jpg" alt="IMG_0425" width="225" height="300" /></a></p>
<p>a bird&#8217;s eye view of our setup<br />
(the large purple areas are audience seating)</p>
<p> </p>
<p><a href="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0424.JPG"><img class="alignnone size-medium wp-image-145" title="IMG_0424" src="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0424-300x225.jpg" alt="IMG_0424" width="300" height="225" /></a></p>
<p>our main interaction screen on the surface</p>
<p> </p>
<p><a href="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0423.JPG"><img class="alignnone size-medium wp-image-144" title="IMG_0423" src="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0423-300x225.jpg" alt="IMG_0423" width="300" height="225" /></a></p>
<p>our main collaborative screen on the surface</p>
<p> </p>
<p><a href="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0426.JPG"><img class="alignnone size-medium wp-image-147" title="IMG_0426" src="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0426-225x300.jpg" alt="IMG_0426" width="225" height="300" /></a></p>
<p>other workspaces</p>
<p> </p>
<p><a href="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0427.JPG"><img class="alignnone size-medium wp-image-148" title="IMG_0427" src="http://www.rebecca-e-spitzer.com/blog/wp-content/uploads/2009/11/IMG_0427-300x225.jpg" alt="IMG_0427" width="300" height="225" /></a></p>
<p>a more detailed interaction storyboard</p>
<p> </p>
<p>More about our proposed changes to come!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rebecca-e-spitzer.com/blog/2009/11/dynamic-rehearsal-project-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
