<?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>Social Interface Agents &#187; Blogs</title>
	<atom:link href="https://icer.x10host.com/wordpress/?cat=20&#038;feed=rss2" rel="self" type="application/rss+xml" />
	<link>https://icer.x10host.com/wordpress</link>
	<description></description>
	<lastBuildDate>Mon, 09 Jun 2014 21:14:03 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.2</generator>
		<item>
		<title>Microsoft Bob and Office Assistants</title>
		<link>https://icer.x10host.com/wordpress/?p=135</link>
		<comments>https://icer.x10host.com/wordpress/?p=135#comments</comments>
		<pubDate>Sat, 07 Jun 2014 09:16:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[Software Agents]]></category>
		<category><![CDATA[clippy]]></category>
		<category><![CDATA[interface agents]]></category>
		<category><![CDATA[microsoft agent]]></category>
		<category><![CDATA[microsoft bob]]></category>
		<category><![CDATA[office assistants]]></category>
		<category><![CDATA[software agents]]></category>

		<guid isPermaLink="false">http://icer.x10host.com/wordpress/?p=135</guid>
		<description><![CDATA[Far from revolutionising human-computer interaction as hoped, Microsoft Bob (Microsoft, 1995), and its infamous descendants[1] 1. Microsoft&#8217;s Utopia project envisaged a revolution in human-computer interaction as profound as the GUI or Desktop metaphor (McCracken, 2010), by a &#8216;natural&#8217; relation to computers via anthropomorphic character interfaces and &#8220;real world&#8221; settings/objects (Fries et. al, 1997). Despite Bob&#8217;s [...]]]></description>
				<content:encoded><![CDATA[<!------------------HELP PANE moved ----------------------------------->
	
 <div id="undercontent" class="undercontent">
 

  <!------------------FAKE TESTING ----------------------------------->
 
 <!----------------------- FAKE DIALOGUE BOX --------------------------->
 <div class="holder">     
      <div id="popup" class="popup">
            <div class="top-content">
            </div>          
            <a href="#" onClick="hidefunc()"><div class="content">
            </div></a>
     </div>
</div>
 <!----------------------- /end FAKE DIALOGUE BOX --------------------------->
 <br />
 
  <!------------------FAKE ESSAY ----------------------------------->
 
<div>

<span id="more-135"></span>

</div>

<div><br />

<!---the essay--->
<p>Far from revolutionising human-computer interaction as hoped, <i>Microsoft</i> <i>Bob </i>(Microsoft, 1995), and its infamous descendants<span class="refcode" id="refintext1"><a href="#footnote1"><sup>[1]</sup></a>
<span class="bigref">
<sup>1.</sup> <i>Microsoft</i>&rsquo;s Utopia project envisaged a revolution in human-computer interaction as profound as the GUI or Desktop metaphor (<a href="http://www.pcworld.com/article/193006/The_Bob_Chronicle">McCracken, 2010</a>), by a &lsquo;natural&rsquo; relation to computers via anthropomorphic character interfaces and &ldquo;real world&rdquo; settings/objects (<a href="http://www.google.com.au/patents/US6388665">Fries et. al, 1997</a>). Despite Bob&rsquo;s (<i>Microsoft</i>, 1995) poor reception, <i>Bob</i>&rsquo;s Guides were transposed directly into Microsoft <i>Office 97</i> (1997) as the <i>Office Assistant</i>, requiring substantial technical prowess to make the same Bob code appear within Office (McCracken, 2009). The 2nd generation of the project, <i>Microsoft Agent</i>, was released to 3rd party developers to create Agent-based application interfaces, and was used in <i>Windows XP</i> (2001) and <i>Office 2003</i> (2003).But <i>Agent</i> support was removed from <i>Windows 7</i> (Microsoft, 2009), and the platform discontinued (<a href="http://support.microsoft.com/kb/969168">&apos;Microsoft Support&apos;, 2012</a>).</span>
</span>, <i>Office Assistants </i>(Microsoft, 1997; 2003), are continually rated among the &apos;worst tech products of all time&apos; (PCWorld, 2006; Time Magazine, 2010). Consumers rejected these software interfaces depicting &apos;familiar&apos; settings like home-office rooms and interactions mediated via semi-autonomous cartoon characters (embodied software agents)<span class="refcode" id="refintext2"><a href="#footnote2"><sup>[2]</sup></a>
<span class="bigref">
<sup>2.</sup>Software agents have a level of autonomy to carry out processing and decisionmaking which is adaptive to the current environment. They carry out goal-directed behaviour, as assigned by a user or program to perform on their behalf, and make their own decisions about when and how to carry out the assigned tasks. Embodied agents, also called Interface Agents, are depicted as an anthropomorphic (&lsquo;embodied&rsquo;) character.</span>
</span>, that <i>Microsoft</i> had assumed would &apos;naturalise&apos;  make familiar, intuitive and accepted  using their software to perform instrumental tasks like wordprocessing or searching.</p>

<p><i>Bob</i> and <i>Office Assistants&apos;</i> failure can partially be blamed on having &quot;patronising&quot; (Van Ittersum, 2008) interfaces, unlikeable characters and problematic interactions. But more problematically, instead of naturalising interfaces and mediation, such embodied-agent and spatial-workroom metaphors became liabilities as taken further, early on continuums toward &apos;realistic&apos; simulation. Such interface paradigms of virtual spatial workplaces also became obsolete generally, and users&apos; expectations in certain task domains perhaps do not correspond with embodied software agents anyway. </p>

<p><i>Bob</i> occurs in <i>Home Shell</i>: a virtual room with furniture, and objects representing the applications, and more rooms accessible by &apos;doors&apos;. <i>Bob</i>&apos;s applications are visual replications of paper-based objects as wordprocessors, lists, spreadsheets etc. All applications are &apos;guided&apos; by an embodied &apos;Assistant&apos; cartoon-character who &apos;talks&apos; in a speech-balloon constantly. Users&apos; inputs occur via selecting options presented within these speech-balloons.</p>
<br />
<p style="text-align:center"><img width="640" height="482" id="Picture2" src="http://icer.x10host.com/wordpress/fig1x.png" alt="Microsoft Bob&apos;s (1995) spatial room/location interface and embodied software Agent cartoon character"></p>
<p style="text-align:center"><b>[Fig. 1]. <i>Microsoft Bob's</i> (1995) spatial room/location interface and embodied software Agent cartoon character.</b></p>
<br />
<p><i>Microsoft</i> envisaged such &quot;real world&quot; 
(Fries et. al, 1997)<span class="refcode" id="refintext3"><a href="#footnote3"><sup>[3]</sup></a>
<span class="bigref">
<sup>3.</sup>Fries et al. (1997) is the patent filed for <i>Microsoft Bob</i>. The developers themselves termed Bob and Assistants a &quot;real world&quot; and &quot;natural&quot;(McCracken, 2010) interface. Possibly the cartoon interface of Bob was implemented because that was the only feasible level of realism with current technical limitations, and the developers still assumed a trajectory toward even greater literal VR-simulation of a spatial office-room would always result in increasingly &lsquo;better&rsquo; HCI (as was a common rhetoric of the time).</span>
</span> interfaces providing a &quot;natural&quot;(McCracken, 2010) relation to computers. Despite probable assumptions that moving toward more accurate simulation of &apos;real&apos; offices made interfaces increasingly more intuitive, their cartoon-like graphics suggest the 'real' here being sought<span class="refcode" id="refintext32"><a href="#footnote3"><sup>[3]</sup></a>
<span class="bigref">
<sup>3.</sup>Fries et al. (1997) is the patent filed for <i>Microsoft Bob</i>. The developers themselves termed Bob and Assistants a &quot;real world&quot; and &quot;natural&quot;(McCracken, 2010) interface. Possibly the cartoon interface of Bob was implemented because that was the only feasible level of realism with current technical limitations, and the developers still assumed a trajectory toward even greater literal VR-simulation of a spatial office-room would always result in increasingly &lsquo;better&rsquo; HCI (as was a common rhetoric of the time).</span>
</span> was not accurate simulation, but increased immediacy (Bolter, 2001), where user-attention to interfaces declines. Replicating  or remediating (Bolter, 2001)already-familiar metaphors like spatial workrooms, paper objects and cartoon-characters was assumed to naturalise attention away from the interface&apos;s mediation, and status as (&apos;unfamiliar&apos;) computer-specific software (Fries et. al, 1997).</p>

<p>Presenting computer applications through spatial room/locations interfaces resembling &apos;real&apos; offices was a common <abbr title="User Interface">UI</abbr> metaphor of the time  but one largely rejected. Consumers not only disliked <i>Bob</i>'s inferior graphics and questionable virtual 'reality'<span class="refcode" id="refintext4"><a href="#footnote4"><sup>[4]</sup></a>
<span class="reftooltip">
<sup>4.</sup>Bob&rsquo;s objects could be moved anywhere, including floating in mid-&lsquo;air&rsquo;.</span>
</span>, but also the graphically-superior <i>Packard Bell Navigator </i>(Lineback, 2013)<span class="refcode" id="refintext5"><a href="#footnote5"><sup>[5]</sup></a>
<span class="reftooltip">
<sup>5.</sup>Swartz (2003) notes Bob's interface was itself inspired by <i>Packard Bell Navigator</i>, but the remediation metaphor of the 'virtual spatial workroom containing office and paper objects' originated in the 1980s with interfaces like <a href="http://books.google.com.au/books?id=gi4EAAAAMBAJ&#038;lpg=PA43&#038;ots=eZ5vsHI_ts&#038;pg=PA43&#038;redir_esc=y#v=onepage&#038;q&#038;f=false"> MagicDesk I (1983)</a>, whose primitive graphics could never be mistaken for attempted 'realism' and are clearly illustrations to help cue usage.</span>
</span>.</p>
<br />
<p style='text-align:center'><img width="601" height="481" id="Picture3" src="http://icer.x10host.com/try/image002.png" alt="Packard Bell Navigator 5's spatial workroom"></p><p style='text-align:center'><b>[Fig. 2]. <i>Packard Bell Navigator 3.5's</i> (1995) spatial workroom had more &apos;realism&apos; in its graphics.</b></p>
<br />
<p>Why were virtual work-rooms rejected? Bolter (2001) understood digital media interfaces through the logics of remediation, which may verify (hypermediacy) <i>or</i> efface (immediacy) the interface and mediation, and replicates older mediums inside it, often portrayed as analogous to older mediums, but <i>better</i>. Greater immediacy is frequently offered as &apos;improvement&apos; over older mediums (Bolter, 2001, pp. 59-62). For example, <i>Bob</i>&apos;s &apos;natural&apos; <abbr title="Human Computer Interaction">HCI</abbr> was claimed more familiar and superior to traditional GUIs (Trower, 2010). </p>

<p>But unlike, say, wordprocessors remediating typewriters but better, 'Home' shells are unambiguously inferior to reality houses and arguably traditional <abbr title="Graphic User Interfaces">GUIs</abbr>. Although remediating &apos;familiar&apos; objects does help cue usage (Kuhn, 1996), virtual-building-based work interfaces generally were hampered by redundancies and limitations imposed by simulating pre-computer &apos;reality&apos;. Since people are experts about real homes and offices, which computer logics cannot effectively remediate, when office/room analogies move toward simulation they seem extremely lacking, and are constrained by expectations of working like working like &apos;reality&apos;<span class="refcode" id="refintext6"><a href="#footnote6"><sup>[6]</sup></a>
<span class="bigref">
<sup>6.</sup>Of course virtual spatial-world interfaces survived for videogames and social environments, but Chao (2001), claims this is because their abstractions are already reductive and alien to users. For example, <a href="http://www.cs.unm.edu/~dlchao/flake/doom/chi/chi.html"> Chao (2001)</a> designed a modification of the <i>Doom</i> game engine for sysadmins to perform the instrumental task of administrating operating system processes, but this was feasible because both operating system processes and the <i>Doom</i> game world are already abstract, and game worlds are not &apos;supposed&apos; to be representations of our mundane reality. Game objects/interfaces may remediate other known media or objects, to cue their uses/interpretation, but the transposition is understood not to be literal.</span>
</span> (Chao, 2001), rather than exploiting specificities of computer technologies. <i>MagicCap</i>'s PDA<span class="refcode" id="refintext7"><a href="#footnote7"><sup>[7]</sup></a>
<span class="reftooltip">
<sup>7.</sup>Portable Digital Assistant. A device somewhat analogous to a modern smartphone used for portable work and communication i.e. productive, work-related activities not tied to specific locations.</span>
</span> <abbr title="Graphic User Interfaces">GUI</abbr> (<i>General Magic</i>, 1994) illustrated these redundancies and limitations. Users must redundantly travel through fixed-plan 'buildings' connected by 'doors' just to get something or do different tasks/applications in other rooms or buildings, even carrying an inventory. Tasks were still direct remediations of paper objects. Computer/database specific functions (e.g. search), unable to be integrated into main interfaces, were accessed under a literal 'magic lamp'. Further taxing spatial workrooms&apos; viability, databases  that Manovich (2002, p. 94; pp. 194-195) credits as the cultural and symbolic form privileged by digital media and the digital age  lacked direct analogues from paper-based offices to remediate. Convoluted patents (Merrick, 1998) resorted to embodied 'Data Machine' objects appearing in these virtual work-rooms, analogous to media player appliances  including in &quot;predicted&quot; (Merrick, 1998) true-<abbr title="Virtual Reality">VR</abbr> virtual offices.</p>

<p align="center" style='text-align:center'><img width="771" height="256" id="Picture23" src="http://icer.x10host.com/wordpress/fig3x.png" alt="General Magic MagicCap (1994)"></p><p align="center"><b>[Fig. 3]. <i>MagicCap's</i> (1994) PDA spatial room/location interface remediated objects and concepts from the physical world. For example, storage on the hard disk/memory card is here depicted as a literal storeroom.</b></p>

<p>Instead, interfaces to/from databases were ultimately returned via webpages and apps (Helmond, 2013)<span class="refcode" id="refintext8"><a href="#footnote8"><sup>[8]</sup></a>
<span class="bigref">
<sup>8.</sup>The Web and subsequent web apps exacerbated the use and impact of databases on ordinary computer users. <a href="http://computationalculture.net/article/the-algorithmization-of-the-hyperlink">Helmond (2013)</a> describes how from Web 2.0 onward, hyperlinks themselves are increasingly a call to a database, not a static webpage.</span>
</span>. Spatial-workroom interfaces were further challenged by the Web, which instead became a frequent interface for users, and subverted intuitive mappings to fixed-spatial geography metaphors. Two way hyperlinks are not trackable, there is no sense of spatial travel between between nodes<span class="refcode" id="refintext9"><a href="#footnote9"><sup>[9]</sup></a>
<span class="bigref">
<sup>9.</sup>The Web, and its underlying network model, makes physical space between nodes (such as webpages or files) conceptually and functionally irrelevant. The physical &lsquo;length&rsquo; of connections between directly linked nodes is effectively zero, regardless of where the objects might be geographically located &ndash; Castells&rsquo; (2001) &lsquo;space of flows&rsquo;. &ldquo;There is no space in Cyberspace&rdquo; (Manovich, 2002, p. 219). Documents are visited directly, not used &lsquo;inside a virtual world&rsquo; and web technology logics support embedding media objects in containers within webpages.</span>
</span>, and every website is linked, not separate &apos;places&apos; like pre-Web BBSs. And since former dichotomies between specific times and places for home/leisure/work further broke down (Levinson, 1999, pp. 132-139), siting specific tasks inside metaphoric &apos;homes&apos; or &apos;offices&apos; was further obsoleted.</p>

<p>Computers themselves became a platform for all activities, including work, where instrumental use of computers is desired. Shneiderman (2005) claims interface functions should feel &apos;invisible&apos; as naturalised tools while used (the opposite of these <i>Assistant</i> Agents). Victor (2006) even advocates limiting agency and interactivity so users better understand <i>all </i>more-limited functions available.</p>

<p>But with a diverse range of desired uses and users of the computer-platform, crippling applications is often inappropriate. <i>Bob</i> and <i>Assistants</i> similarly did not assume diverse ranges of users and uses: the patronising <i>Assistants</i> were on by default and did not adapt to individual users. Although critics of tool-like &apos;software appliances&apos; claim users instead desire experiences(Bolter, 2003, pp. 104-112), users also disliked the experience of <i>Assistants </i>(Serenko et. al., 2007)<span class="refcode" id="refintext10"><a href="#footnote9"><sup>[10]</sup></a>
<span class="bigref">
<sup>10.</sup>Serenko&rsquo;s (2007) <a href="http://www.business.mcmaster.ca/mktg/nbontis/ic/publications/SerenkoBontisDetlorBIT.pdf">study</a> found averages of &lsquo;perceived enjoyment&rsquo;, &lsquo;perceived usefulness&rsquo; and &lsquo;intention to use&rsquo; toward Assistants among users were all &ldquo;very low&rdquo;.</span>
</span>.</p>
<p>Coleman (2011, pp. 28-31) claimed character-interfaces failed generally because their behaviours were not adequately humanlike. But <i>Microsoft</i> remediated <i>non</i>-human cartoon-characters<span class="refcode" id="refintext11"><a href="#footnote11"><sup>[11]</sup></a>
<span class="bigref">
<sup>11.</sup>Serenko&rsquo;s (2007) <a href="http://www.business.mcmaster.ca/mktg/nbontis/ic/publications/SerenkoBontisDetlorBIT.pdf">research</a> found users did associate Assistants&rsquo; cartoon-characters with animated movies, thus suggesting this remediation of cartoons was &lsquo;successful&rsquo; in the sense people drew such association of &lsquo;familiarity&rsquo;. (He did not study comics.) He further found <a href="http://www.aserenko.com/papers/Serenko_Animation_Scale.pdf">also enjoying animated films</a> correlated with being more accepting of Assistants, although noted that overall perceived enjoyment and usefulness of Assistants was still &quot;very low&quot;.</span>
</span> deliberately (Seaward, 1998), since people accept greater deviations by those characters. People respond favourably to cartoon and simplistic characters in <i>other</i> contexts, e.g. nurturing subordinates (Turkle, 2008, pp. 132-134). </p>

<p>Non-humanlikeness alone cannot explain <i>Assistants</i>&apos; rejection. Do most people want &apos;assistance&apos; from agent-characters in such situations at <i>all</i>? A software agent is <i>not</i> user-agency. And unlike human secretaries doing unwanted tasks delegated to them, many agents are there because users do not know how to accomplish desired tasks themselves, or are not permitted to.</p>

<p>Swartz (2003) identified two main problems with <i>Assistants</i>. They were status-lowering, by reminding beginners how much they did not know and insinuating advanced users needed assistance. And they were distracting  even users who liked them did because the animations amused them when they were bored working.</p>

<p><i>Assistants</i> did not behave like instrumental &apos;tools&apos;, or subordinates, but exerted their <i>own</i> agency, subordinating users. The cartoons being remediated (Pugh, 2012)<span class="refcode" id="refintext12"><a href="#footnote12"><sup>[12]</sup></a>
<span class="bigref">
<sup>12.</sup>Pugh (2012) decides comics and cartoons are already hypermediated forms. Pugh (2012) also observes <i>Disney</i> animated films remediated other artistic traditions depicting &lsquo;nature&rsquo;, not actual &lsquo;nature&rsquo;. This supports the notion an interface featuring anthropomorphic cartoon characters cannot be considered a &ldquo;real world&rdquo; interface as <i>Microsoft&rsquo;s </i>patents claimed, and the &lsquo;real&rsquo; being sought was thus an more immediate relation to the interface, with less attention to its mediation, and status as computer software. </span>
</span> do <i>not</i> have such repercussions to viewers of characters&apos; actions. Bolter (2001, p.27) observes software <i>usually</i> effaces its own programming decisions from users. Instead, this interface&apos;s removal of user-control was believed to be &apos;justified&apos; and made acceptable to users  naturalised  by personifying it as &apos;autonomous&apos; actors. Users never have complete control of applications/interfaces, but ironically, this personification exacerbated attention toward such non-control, and the interface itself  rupturing attempted immediacy into unintended hypermediacy (Bolter, 2001). Remediating embodied characters merely naturalised obvious targets for users&apos; attention and negativity.</p>

<p>This may partially explain why recently favoured 'invisible'<span class="refcode" id="refintext13"><a href="#footnote13"><sup>[13]</sup></a>
<span class="bigref">
<sup>13.</sup>'Invisible' in the sense of not having a visible body, or even a persona at all. Voice-only <i>Siri</i> (Apple, 2011) may remediate the better-naturalised <a href="http://www.alluvium-journal.org/2012/10/01/androids-in-the-academy/"> 'absent body' like a remote assistant (Dinnen, 2012)</a>, other software agents are not personified.</span>
</span> agents (e.g. <i>Siri (</i>Apple, 2011), <i>Googlebot </i>(Google, 1998)) are better accepted by users, but these are criticised as not presenting accurate or enough information for users to make their own decisions (Bolter, 2003, pp. 52-55) users may take <i>non</i>-embodied agents&apos; &apos;decisions&apos; for granted, even when not understanding, predicting, controlling, or even noticing agents&apos; actions (Shneiderman, 1997). Despite visible failures of cartoon Agents, influences of better-naturalised &apos;invisible&apos; agents receive less direct attention. When not anthropomorphised they are not perceived &apos;Agents&apos; but just &apos;information&apos;.</p>

<p>Interface metaphors influence users&apos; conceptualisations of technologies (Manovich, 2001). Software agents&apos; processing does not really bear analogy to anthropomorphic characters/actors. This metaphor is also remediation to naturalise and justify embodying software agents&apos; actions/&apos;decisions&apos; outside users&apos; direct control, and when poorly executed it was not accepted. Bolter (2003, pp. 88-89) observes that as &apos;new&apos; media/technologies become normalised, direct remediations decline. Both character-agent and spatial office-room metaphors broke down as taken further, so have since been abstracted away from physical embodiment<span class="refcode" id="refintext13"><a href="#footnote14"><sup>[14]</sup></a>
<span class="bigref">
<sup>14.</sup>As well as <i>Apple</i>&apos;s voice-only <i>Siri</i> (2011), Microsoft&apos;s Cortana (2014) assistant&apos;s only visuals are a <a href="http://www.theverge.com/2014/3/4/5470592/cortana-windows-phone-8-1-video-demo">very-abstracted circle animation (Warren, 2014)</a>.</span>
</span>. But &apos;invisible&apos; agents have not resolved the question of when it is appropriate  or inappropriate  to delegate user-control to agents, or other metaphors, at all.</p>

<p>&nbsp;</p>

<h3><b>&nbsp;REFERENCES:</b></h3>

<p>Bolter, J. D., &amp; Grusin, R. (2001). <i>Remediation: Understanding new media</i>.
Cambridge, Mass: MIT Press.</p>

<p>Bolter, J. D., &amp; Gromala, D. (2003). <i>Windows and mirrors: Interaction design, digital art,
and the myth of transparency</i>. Cambridge, Mass: MIT Press.</p>
<p>Castells, M. (2010). <i>The rise of the network society</i> (2nd ed.). Oxford: Wiley-Blackwell.</p>

<p>Chao, D. (2001, March). Doom as an interface for process
management. In <i>Proceedings of the SIGCHI
conference on Human factors in computing systems. </i>Paper presented at
CHI 2001 Conference on Human Factors in Computing Systems, Seattle, WA, 31
March - 5 April (pp. 152-157). New York, NY: ACM. Retrieved from:
http://www.cs.unm.edu/~dlchao/flake/doom/chi/chi.html [Accessed: 4 May 2014].</p>

<p>Dinnen, Z. (2012). Androids in the academy. <i>Alluvium, 1</i>(5). <a href="http://dx.doi.org/10.7766/alluvium.v1.5.03">http://dx.doi.org/10.7766/alluvium.v1.5.03</a></p>

<p>Farber, D. (2013). Bill Gates says Microsoft Bob will make a
comeback. <i>CNET</i> [online].
Retrieved from:

http://news.cnet.com/8301-10805_3-57593736-75/bill-gates-says-microsoft-bob-will-make-a-comeback/

[Accessed: 11 May 2014].</p>

<p>Fletcher, D. (2010, May 27). The 50 worst inventions.
Microsoft BOB. <i>TIME Magazine</i>.
[online] Retrieved from:

http://content.time.com/time/specials/packages/article/0,28804,1991915_1991909_1991855,00.html

[Accessed: 4 May 2014].</p>

<p>Fries, K., Linnett, B., &amp; Powelson, L. (1997). Software
platform having a real world interface with animated characters. U.S. Patent
No. 5,682,469. Washington, DC: U.S. Patent and Trademark Office.</p>

<p>Gentilviso, C. (2010, May 27). The 50 worst inventions.
Clippy. <i>TIME Magazine</i>. [online]
Retrieved from:

http://content.time.com/time/specials/packages/article/0,28804,1991915_1991909_1991755,00.html

[Accessed: 4 May 2014].</p>

<p>Hall, L. (2001) Social Interface Agents. [online] Retrieved
from: <a href="http://computing.unn.ac.uk/staff/cglh1/MSc%20HCI/Social%20Interface%20Agents.ppt">http://computing.unn.ac.uk/staff/cglh1/MSc%20HCI/Social%20Interface%20Agents.ppt</a></p>

<p>Helmond, A. (2013). The Algorithmization of the Hyperlink. <i>Computational Culture, 3.</i></p>

<p>Kuhn, W. (1996, August). Handling data spatially:
Spatializating user interfaces. In <i>Advances
in GIS research II: Proceedings of the 7th International Symposium on Spatial
Data Handling</i> (Vol. 2, p. 13B). Retrieved from: <a href="http://www.geog.ucsb.edu/~sara/teaching/geo234_02/papers/kuhn_sdh96.pdf">http://www.geog.ucsb.edu/~sara/teaching/geo234_02/papers/kuhn_sdh96.pdf</a>
[Accessed: 4 May 2014].</p>

<p>Levinson, P. (1999) Chapter 11. Serfs to surf. In <i>Digital McLuhan: A Guide to the Information
Millennium</i> (pp. 132140). New York : Routledge </p>

<p>Lineback, N. (2013). Packard Bell Navigator 3.5. The
Graphical User Interface Gallery [online] Retrieved from:
http://toastytech.com/guis/pbnav35.html [Accessed: 9 May 2014].</p>

<p>Manovich, L. (2001). The interface. Interface Explorer -
shared boundaries. [online] Retrieved from:
http://interface.t0.or.at/levmessay.html [Accessed: 10 May 2014].</p>

<p>Manovich, L. (2002). <i>The
language of new media</i>. Cambridge, Mass: MIT Press.</p>

<p>McCracken, H. (2009). The Secret Origins of Clippy:
Microsoft&apos;s Bizarre Animated Character Patents. <i><span style='font-style: italic'>PCWorld</i>. Retrieved from:
http://technologizer.com/2009/01/02/microsoft-clippy-patents/10/[Accessed 19
May 2014].</p>

<p>McCracken, H. (2010). The Bob Chronicles. <i>PCWorld</i>. Retrieved from:
http://www.pcworld.com/article/193006/The_Bob_Chronicles.html?page=0 [Accessed
19 May 2014].</p>

<p>Merrick, R., &amp; Richards, J. (1998). Virtual office with
connections between source data machine, and a viewer objects. U.S. Patent No.
5,808,612. Washington, DC: U.S. Patent and Trademark Office. Retrieved from:
http://www.google.com.au/patents?id=NHsnAAAAEBAJ [Accessed: 4 May 2014].</p>

<p>Merrit, T. (2007). Top 10 worst products. <i>CNET</i>. [online] Retrieved from: <a href="https://web.archive.org/web/20130404070656/http:/www.cnet.com/1990-11136_1-6313439-1.html">https://web.archive.org/web/20130404070656/http://www.cnet.com/1990-11136_1-6313439-1.html</a>
[Accessed: 4 May 2014].</p>

<p>Microsoft. (2012). Microsoft Agent-enabled programs do not
work in Windows 7. Retrieved from: http://support.microsoft.com/kb/969168
[Accessed 4 May 2014].</p>

<p>Pugh, T., &amp; Aronstein, S. L. (2012). <i>The Disney Middle Ages: A fairy-tale and fantasy past</i>
(pp. 199-200). New York: Palgrave Macmillan.</p>

<p>Robinson, P. (1984, February). Review: Magic Desk<i>. InfoWorld, 6</i>(7), pp. 43-44. Retrieved
from:

http://books.google.com.au/books?id=gi4EAAAAMBAJ&#038;lpg=PA43&#038;ots=eZ5vsHI_ts&#038;pg=PA43&#038;redir_esc=y#v=onepage&#038;q&#038;f=false</p>

<p>Robotzeitgeist.com. (2009). The Lumiere project: the origins
and science behind Microsoft&apos;s Office Assistant. Robotics Zeitgeist [online]
Retrieved from:

http://robotzeitgeist.com/2009/08/lumiere-project-origins-and-science.html

[Accessed: 11 May 2014].</p>

<p>Seaward, M. (1998). Interactive assistants provide ease of
use for novices: the development of prototypes and descendants. <i>Computers in human behavior, 14</i>(2),
221-237.</p>

<p>Serenko, A., Bontis, N., &amp; Detlor, B. (2007). End-user
adoption of animated interface agents in everyday work applications. <i>Behaviour &amp; Information Technology, 26</i>(2),
119-132.</p>

<p>Serenko, A. (2007b). The development of an instrument to
measure the degree of animation predisposition of agent users. <i>Computers in human behavior, 23</i>(1),
478-495.</p>

<p>Shneiderman, B., &amp; Maes, P. (1997). Direct manipulation
vs. interface agents. <i>Interactions, 4</i>(6),
42-61. Retrieved from: <a href="http://ritter.ist.psu.edu/misc/dirk-files/Papers/HRI-papers/User%20interface%20design%20issues/Direct%20manipulation%20vs.%20interface%20agents.pdf">http://ritter.ist.psu.edu/misc/dirk-files/Papers/HRI-papers/User%20interface%20design%20issues/Direct%20manipulation%20vs.%20interface%20agents.pdf</a>
[Accessed: 9 May 2014].</p>

<p>Swartz, L. (2003). <i>Why
people hate the paperclip: labels, appearance, behavior, and social responses
to user interface agents</i> (Dissertation, Stanford University).
Retrieved from: http://xenon.stanford.edu/~lswartz/paperclip/ [Accessed: 4 May
2014].</p>

<p>Tofel, K. (2011). Could Siri be the invisible interface of
the future?. [online] Retrieved from:

http://gigaom.com/2011/10/25/could-siri-be-the-invisible-interface-of-the-future/

[Accessed: 8 May 2014].</p>

<p>Trower, T. (2010). Bob and Beyond: A Microsoft Insider
Remembers. <i>Technologizer.</i>
Retrieved from: from:

http://technologizer.com/2010/03/29/bob-and-beyond-a-microsoft-insider-remembers/

[Accessed 26 Apr 2014].</p>

<p>Turkle, S. (2008).
Always-on/always-on-you: The tethered self. In Katz, J. E. (Ed.), <i>Handbook of Mobile Communication Studies</i> (pp. 121-137). Cambridge, Mass: MIT Press.</p>

<p>Tynan, D. (2006, May 26). The 25 worst tech products of all
time. <i>PC World</i>. [online]
Retrieved from: http://www.pcworld.com/article/125772/worst_products_ever.html
[Accessed: 4 May 2014].</p>

<p>Van Ittersum, D. (2008). Computing Attachments: Engelbart's
Controversial Writing Technology. <i>Computers
and Composition, 25</i>(2), 143-164. Retrieved from: <a href="http://faculty.kent.edu/craigr/65012/Articles/VanIttersum%202007.pdf">http://faculty.kent.edu/craigr/65012/Articles/VanIttersum%202007.pdf</a>
[Accessed: 4 May 2014].</p>

<p>Victor, B. (2006). Magic ink: information software and the
graphical interface. [online] Retrieved from: http://worrydream.com/MagicInk/
[Accessed: 11 May 2014].</p>

<p>Warren, T. (2014). Microsoft's Siri-like Cortana assistant demonstrated
on video. [online] Retrieved from:

http://www.theverge.com/2014/3/4/5470592/cortana-windows-phone-8-1-video-demo

[Accessed: 20 Apr 2014].</p>

<p><h3>&nbsp;<b>SOFTWARE</b></h3></p>

<p>Apple. (2011). <i>Siri</i>
[iOS Software]. Apple.</p>

<p>General Magic. (1994). <i>Magic
Cap</i> [Computer Software]. General Magic.</p>

<p>Microsoft. (1995). <i>Microsoft
Bob</i> [PC Software]. Microsoft.</p>

<p>Microsoft. (1997; 2002). <i>Microsoft
Agent</i> [PC Software]. Microsoft.</p>

<p>Microsoft. (2003). <i>Microsoft
Office 2003</i> [PC Software]. Microsoft.</p>

<p>Microsoft. (2014) <i>Cortana</i>
[Windows Phone software]. Microsoft.</p>

<p>Packard Bell. (1995). <i>Packard
Bell Navigator (Version 3.5)</i> [PC Software]. Packard Bell.</p>

<p>&nbsp;</p>
<hr />
<!--end the essay-->
<h3>&nbsp;FOOTNOTES</h3>

<br />
<p id="footnote1"><a href="#refintext1">
<sup>[1]</sup></a> <i>Microsoft</i>&rsquo;s Utopia project envisaged a revolution in human-computer interaction as profound as the GUI or Desktop metaphor (<a href="http://www.pcworld.com/article/193006/The_Bob_Chronicle">McCracken, 2010</a>), by a &lsquo;natural&rsquo; relation to computers via anthropomorphic character interfaces and &ldquo;real world&rdquo; settings/objects (<a href="http://www.google.com.au/patents/US6388665">Fries et. al, 1997</a>). Despite Bob&rsquo;s (<i>Microsoft</i>, 1995) poor reception, <i>Bob</i>&rsquo;s Guides were transposed directly into Microsoft <i>Office 97</i> (1997) as the <i>Office Assistant</i>, requiring substantial technical prowess to make the same Bob code appear within Office (McCracken, 2009). The 2nd generation of the project, <i>Microsoft Agent</i>, was released to 3rd party developers to create Agent-based application interfaces, and was used in <i>Windows XP</i> (2001) and <i>Office 2003</i> (2003).But <i>Agent</i> support was removed from <i>Windows 7</i> (Microsoft, 2009), and the platform discontinued (<a href="http://support.microsoft.com/kb/969168">&apos;Microsoft Support&apos;, 2012</a>).</p>

<p id="footnote2"><a href="#refintext2">
<sup>[2]</sup></a>Software agents have a level of autonomy to carry out processing and decisionmaking which is adaptive to the current environment. They carry out goal-directed behaviour, as assigned by a user or program to perform on their behalf, and make their own decisions about when and how to carry out the assigned tasks. Embodied agents, also called Interface Agents, are depicted as an anthropomorphic (&lsquo;embodied&rsquo;) character.</p>
<p id="footnote3"><a href="#refintext3">
<sup>[3]</sup></a>Fries et al. (1997) is the patent filed for <i>Microsoft Bob</i>. The developers themselves termed Bob and Assistants a &quot;real world&quot; and &quot;natural&quot;(McCracken, 2010) interface. Possibly the cartoon interface of Bob was implemented because that was the only feasible level of realism with current technical limitations, and the developers still assumed a trajectory toward even greater literal VR-simulation of a spatial office-room would always result in increasingly &lsquo;better&rsquo; HCI (as was a common rhetoric of the time).</p>

<p id="footnote4"><a href="#refintext4">
<sup>[4]</sup></a>Bob&rsquo;s objects could be moved anywhere, including floating in mid-&lsquo;air&rsquo;.</p>


<p id="footnote5"><a href="#refintext5">
<sup>[5]</sup></a>Swartz (2003) notes Bob's interface was itself inspired by <i>Packard Bell Navigator</i>, but the remediation metaphor of the 'virtual spatial workroom containing office and paper objects' originated in the 1980s with interfaces like <a href="http://books.google.com.au/books?id=gi4EAAAAMBAJ&#038;lpg=PA43&#038;ots=eZ5vsHI_ts&#038;pg=PA43&#038;redir_esc=y#v=onepage&#038;q&#038;f=false"> MagicDesk I (1983)</a>, whose primitive graphics could never be mistaken for attempted 'realism' and are clearly illustrations to help cue usage.</p>



<p id="footnote6"><a href="#refintext6">
<sup>[6]</sup></a>Of course virtual spatial-world interfaces survived for videogames and social environments, but Chao (2001), claims this is because their abstractions are already reductive and alien to users. For example, <a href="http://www.cs.unm.edu/~dlchao/flake/doom/chi/chi.html">Chao (2001)</a> designed a modification of the <i>Doom</i> game engine for sysadmins to perform the instrumental task of administrating operating system processes, but this was feasible because both operating system processes and the <i>Doom</i> game world are already abstract, and game worlds are not &apos;supposed&apos; to be representations of our mundane reality. Game objects/interfaces may remediate other known media or objects, to cue their uses/interpretation, but the transposition is understood not to be literal.</p>
<p id="footnote7"><a href="#refintext7">
<sup>[7]</sup></a>Portable Digital Assistant. A device somewhat analogous to a modern smartphone used for portable work and communication i.e. productive, work-related activities not tied to specific locations.</p>
<p id="footnote8"><a href="#refintext8">
<sup>[8]</sup></a>The Web and subsequent web apps exacerbated the use and impact of databases on ordinary computer users. <a href="http://computationalculture.net/article/the-algorithmization-of-the-hyperlink">Helmond (2013)</a> describes how from Web 2.0 onward, hyperlinks themselves are increasingly a call to a database, not a static webpage.</p>

<p id="footnote9"><a href="#refintext9">
<sup>[9]</sup></a>The Web, and its underlying network model, makes physical space between nodes (such as webpages or files) conceptually and functionally irrelevant. The physical &lsquo;length&rsquo; of connections between directly linked nodes is effectively zero, regardless of where the objects might be geographically located &ndash; Castells&rsquo; (2001) &lsquo;space of flows&rsquo;. &ldquo;There is no space in Cyberspace&rdquo; (Manovich, 2002, p. 219). Documents are visited directly, not used &lsquo;inside a virtual world&rsquo; and web technology logics support embedding media objects in containers within webpages.</p>


<p id="footnote10"><a href="#refintext10">
<sup>[10]</sup></a>Serenko&rsquo;s (2007) <a href="http://www.business.mcmaster.ca/mktg/nbontis/ic/publications/SerenkoBontisDetlorBIT.pdf">study</a> found averages of &lsquo;perceived enjoyment&rsquo;, &lsquo;perceived usefulness&rsquo; and &lsquo;intention to use&rsquo; toward Assistants among users were all &ldquo;very low&rdquo;.</p>


<p id="footnote11"><a href="#refintext11">
<sup>[11]</sup></a>Serenko&rsquo;s (2007) <a href="http://www.business.mcmaster.ca/mktg/nbontis/ic/publications/SerenkoBontisDetlorBIT.pdf">research</a> found users did associate Assistants&rsquo; cartoon-characters with animated movies, thus suggesting this remediation of cartoons was &lsquo;successful&rsquo; in the sense people drew such association of &lsquo;familiarity&rsquo;. (He did not study comics.) He further found <a href="http://www.aserenko.com/papers/Serenko_Animation_Scale.pdf">also enjoying animated films</a> correlated with being more accepting of Assistants, although noted that overall perceived enjoyment and usefulness of Assistants was still &quot;very low&quot;.</p>

<p id="footnote12"><a href="#refintext12">
<sup>[12]</sup></a>Pugh (2012) decides comics and cartoons are already hypermediated forms. Pugh (2012) also observes <i>Disney</i> animated films remediated other artistic traditions depicting &lsquo;nature&rsquo;, not actual &lsquo;nature&rsquo;. This supports the notion an interface featuring anthropomorphic cartoon characters cannot be considered a &ldquo;real world&rdquo; interface as <i>Microsoft&rsquo;s </i>patents claimed, and the &lsquo;real&rsquo; being sought was thus an more immediate relation to the interface, with less attention to its mediation, and status as computer software.</p>

<p id="footnote13"><a href="#refintext13">
<sup>[13]</sup></a>'Invisible' in the sense of not having a visible body, or even a persona at all. Voice-only <i>Siri</i> (Apple, 2011) may remediate the better-naturalised <a href="http://www.alluvium-journal.org/2012/10/01/androids-in-the-academy/"> 'absent body' like a remote assistant (Dinnen, 2012)</a>, other software agents are not personified.</p>

<p id="footnote14"><a href="#refintext14">
<sup>[14]</sup></a>As well as <i>Apple</i>&apos;s voice-only <i>Siri</i> (2011), Microsoft&apos;s Cortana (2014) assistant&apos;s only visuals are a <a href="http://www.theverge.com/2014/3/4/5470592/cortana-windows-phone-8-1-video-demo">very-abstracted circle animation (Warren, 2014)</a>.</p>
</div>
</div>
 <!------------------/END MAIN CONTENT DIV ----------------------------------->
<!---SHOW/HIDE CLIPPY BUTTON----------------------->
<div class="showhide" id="showhide">
	<a href="#" onClick="showclippy()"><img src="show.png" style="width: 119px; height: 25px;"></a>
</div>

	<!-- Add these scripts to  the bottom of the page -->
<!-- jQuery 1.7+ -->
<!-- Clippy.js -->
<script src="clippyjs-z-partmini.js"></script>

<!-- Clippy Init script -->
<script type="text/javascript">


 /**********************LOAD CLIPPY AND CLIPPY'S JS FILE************************/	
	clippy.load('Clippy', function(agent) {
        // Do anything with the loaded agent
        agent.show();
	
		agent.speak('<p>Greetings. I am Clippit aka Clippy, the pinnacle of Microsoft Agent Office Assistant technology. Move your mouse over me any time for help!</p><p>It looks like you&#39;re reading this page. Would you like help?</p> <img src="officebullet.gif">&nbsp;<a onClick="testFunc(10)" href="#"><b>Help me.</b></a><br /> <img src="officebullet.gif">&nbsp;<a onclick="testFunc(2)" href="#"><b>Just read the page without help.</b></a><br /><br />');

		agent.animate();
		initover=1;
		$(document).on('hideclippyEvent', function() {
			//alert("hideclippyEvent");
			//agent.play('SendMail');
		});
	

	
	});
</script>		

<script type="text/javascript">
if(rover==1){
	clippy.load('Rover', function(agent) {
        // Do anything with the loaded agent
		
        agent.show();
		

	});
}
</script>

 <script type="text/javascript">
 /**********************SELECTION MENU************************/
$(function(){
    $.contextMenu({
        selector: '.clippy', 
		/* on mouseover */
		trigger: 'hover',
        delay: 500,
        autoHide: true,
		
        build: function($trigger, e) {
            // this callback is executed every time the menu is to be shown
            // its results are destroyed every time the menu is hidden
            // e is the original contextmenu event, containing e.pageX and e.pageY (amongst other data)
            return {
                callback: function(key, options) {
                    var m = "clicked: " + key;
                    
					
					if(key=="using"){
						
						/*alert("You can access the Assistant Menu by holding the mouse over the assistant. \n \n You can move the Assistant anywhere on the screen by clicking on it, holding down the mouse button and dragging it to a new location. \n \n You can set Options by choosing Options.");*/
						fakeDialoguefunc('optionsdialog');
					}
					
					if(key=="help"){
						
						/*execute clippy's default help*/
						newFunc();
						$(document).trigger("helpEvent");
						
					
					}
					
					
					if(key=="animate"){
					
					
					}
					
					if(key=="options"){
				
						/*soundSwitch();*/
					
					}
					
										
					if(key=="sound"){
						
						/*alert("sound");*/
						soundSwitch();
					
					}
					
					if(key=="change"){
						
						/*alert("change");*/
						changeAssistant();
					
					}
					
					if(key=="hide"){
						
						/*alert("change");*/
						hideclippy();
					
					}
					
					if(key=="about"){
						
						fakeDialoguefunc('aboutdialog');
					
					}
					
					
                },
			items: {
				"help": {name: "&nbsp; Help me!", icon: "help"},
				"animate": {name: " &nbsp; Animate!", icon: "animate"},
				"using": {name: " &nbsp; Using the Office Assistant...", icon: "using"},
				"sep1": "---------",
				"fold1": {
					"name": " &nbsp; Options...", icon: "options", 
					"items": {
						"sound": {"name": " &nbsp; Turn "+soundtoggletext+" sound"},
						"change": {"name": " &nbsp; Change Assistant..."},
						"sep2": "---------",
						"hide": {"name": " &nbsp; Hide"}
					}
				
				},
				"sep3": "---------",
				"about": {"name": " &nbsp; About..."}
				
                }
            };
        }
    });
}); 
 /********************** END SELECTION MENU************************/
</script>

<script type="text/javascript">	
 /**********************FAKE DIALOGUE BOXES************************/
	function fakeDialoguefunc(dialoguename) {
	
	/* replace html in contentdiv with the right one*/
	/*change the width and height to the right one*/

	var temphtml='<div class="top-content"></div><a href="#" onClick="hidefunc()"><div class="content" id="content"><img src="'+dialoguename+'.png" style="padding:0; margin:0; line-height:0px;"></div></a>';
	
	/*check image size*/
	var img = new Image();
	img.src = dialoguename+'.png';
	img.onload = function() {
		/* alert('height: ' + img.height + ' width: ' + img.width); */
		tempheight=img.height;
		tempwidth=img.width;
		/* alert(tempheight+":"+tempwidth); */
		
		
			/*change everything to the right dimensions*/
		$( "#popup" ).css( "width", tempwidth+"px" );
		$( "#popup" ).css( "margin-left", "-"+(tempwidth/2)+"px" );
		$( "#popup" ).css( "margin-top", "-"+(tempheight/2)+"px" );
		$( "#content" ).css( "background-image", "" );	
		$( "#content" ).css( "height", tempheight+"px" );	
		
		
		document.getElementById('popup').innerHTML=temphtml; 
		//alert($( "#popup" ).css( "margin-left", "-"+(tempwidth/2)+"px" ));
		//alert($( "#content" ).css( "height"));
		//alert("new margin top not -69"+$( "#popup" ).css( "margin-top"));
		//alert($( "#content" ).css( "height"));
		
		$( ".holder" ).show(); 
		/*put on top*/
		$( ".holder" ).css( "z-index", "9100" );	
		
	};
	
	
	
	
	
	
	/* document.getElementById('popup').innerHTML=temphtml; 
	
	
	$( ".holder" ).show(); */
	
	
	
	} 
	/**********************HIDE DIALOGUE BOXES************************/	
	function hidefunc(dialoguename) {
	
		$( ".holder" ).hide();
		$( ".holder" ).css( "z-index", "0" );
		$( '.clippy-balloon' ).css( 'z-index', '1000' );	
		$( '.clippy' ).css( 'z-index', '1000' );		
	} 
	
	 /**********************CHANGE ASSISTANT BOX************************/
	function changeAssistant(assistant) {
	
		$( ".holder" ).hide(); /*in case dialogue is already out, is this bad? the old alerts should still be there?*/
		/* replace html in contentdiv with the right one*/
	
		//clippy
		var temphtml='<div class="top-content"></div><div class="content"><div style="padding:0; margin:0; vertical-align:top; display:inline-block; line-height:0px;"><img src="clippychange1-01.png" width="485" height="22" style="padding:0; margin:0; line-height:0px;"><a href="#" onClick="hidefunc()"><img src="clippychange1-02.png" width="22" height="22" style="padding:0; margin:0; line-height:0px;"></a></div><div style="padding:0; margin:0; vertical-align:top; display:inline-block; line-height:0px;"><img src="clippychange1-03.png" width="507" height="232" style="padding:0; margin:0; line-height:0px;"></div><div style="padding:0; margin:0; vertical-align: top; display:inline-block; line-height:0px;"><img src="clippychange2.png" style="padding:0; margin:0;"><a href="#" onClick="changeAssistant(\'rover\')"><img src="clippychange3.png" style="padding:0; margin:0; border:0;"></a><img src="clippychange4.png" style="padding:0; margin:0;"><a href="#" onClick="hidefunc()"><img src="clippychange5.png" style="padding:0; margin:0;"><img src="clippychange6.png" style="padding:0; margin:0; vertical-align:top;"></a></div></div>';
		
		
		if (assistant=="rover"){
			var temphtml='<div class="top-content"></div><div class="content"><div style="padding:0; margin:0; vertical-align: top; display:inline-block; line-height:0px;"><img src="roverchange1.png" style="padding:0; margin:0; line-height:0px;"></div><div style="padding:0; margin:0; vertical-align: top; display:inline-block; line-height:0px;"><a href="#" onClick="changeAssistant()"><img src="roverchange2.png" style="padding:0; margin:0;"></a><a href="#" onClick="fakeDialoguefunc(\'errorbox\')"><img src="roverchange3.png" style="padding:0; margin:0; border:0;"></a><a href="#" onClick="changeAssistant()"><img src="roverchange4.png" style="padding:0; margin:0;"></a></div><div><img src="roverchange5.png" style="padding:0; margin:0;"><a href="#" onClick="fakeDialoguefunc(\'errorbox\')"><img src="roverchange6.png" style="padding:0; margin:0;"></a><a href="#" onClick="hidefunc()"><img src="roverchange7.png" style="padding:0; margin:0;"></a></div></div>';
		}
	
		
		/*change everything to the right dimensions*/
		$( "#popup" ).css( "width", "507px" );
		$( "#popup" ).css( "margin-left", "-254px" );
		$( "#popup" ).css( "margin-top", "-170px" );
		$( "#content" ).css( "background-image", "" );	
		$( "#content" ).css( "height", "341px" );	
	
		document.getElementById('popup').innerHTML=temphtml; //works
		/*try multiple*/
		/*maybe make each have its own named div*/
		/*document.getElementById('popup').innerHTML+=temphtml; */
		$( ".holder" ).show();
		
	} 
 /**********************END DIALOGUE SCRIPTS************************/
</script>

<script type="text/javascript">
	/**********************HIDE ANYTHING FUNC************************/
	/*script to hide any passed in element*/
	function closefunc(windowname) {

		var currentwindow=document.getElementById(windowname);
		/*$( ".holder" ).show(); */

		$(currentwindow).hide(); 
		
		if(windowname=="mshelpwindow"){
			//change the content div to not be around it
			$( "#undercontent" ).css( "width", "100%" );
		}
		
		
		/*document.getElementById("mshelpwindow")*/
		/*$( "#mshelpwindow" ).css( "display", "none" );	*/
		$( '.clippy-balloon' ).css( 'z-index', '1000' );
		$( '.clippy' ).css( 'z-index', '1000' );
	}
</script>

<script type="text/javascript">

/**************TEMP HELP WINDOW FUNC (REPLACED?)**********/
	function helpwindowtop(changetype) {
	
		var changetodo=changetype;
		
		if (changetodo=="show"){
		
			$( '#mshelpwindow' ).css( 'z-index', '9001' );
			$( '.clippy-balloon' ).css( 'z-index', '-1' );
			/*try*/
			$( '.clippy-balloon' ).css( 'z-index', '1' );			
			var tempzindex=$( '.clippy-balloon' ).css( 'z-index');
		}
		
		if (changetodo=="hide"){
		
			$( '#mshelpwindow' ).css( 'z-index', '9001' );
			$( '.clippy-balloon' ).css( 'z-index', '9002' );
			var tempzindex=$( '.clippy-balloon' ).css( 'z-index');
			
		}

	} 
</script>]]></content:encoded>
			<wfw:commentRss>https://icer.x10host.com/wordpress/?feed=rss2&#038;p=135</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
