<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Why the WIMP User Interface is Dead? (for information retrieval)</title>
	<atom:link href="http://www.sastwingees.org/2006/05/21/why-the-wimp-user-interface-is-dead-for-information-retrieval/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sastwingees.org/2006/05/21/why-the-wimp-user-interface-is-dead-for-information-retrieval/</link>
	<description>Knowledge is Scrumptious</description>
	<lastBuildDate>Tue, 09 Feb 2010 13:35:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.sastwingees.org/2006/05/21/why-the-wimp-user-interface-is-dead-for-information-retrieval/comment-page-1/#comment-183</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 22 May 2006 05:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/2006/05/21/why-the-wimp-user-interface-is-dead-for-information-retrieval/#comment-183</guid>
		<description>Ganesh,

Thanks for the comments.

1. Yes, you are right in the sense that WIMP will not die that easily and it should not because it does offer significant productivity improvements.

2. I am only arguing that Search could be a unifying metaphor for the various app silos in the Enterprise. Its not necessary that it has to be one button.  Therefore, when you use Onebox search, you can do simple searches and using Advanced Search you can do slightly more advanced searches. The search string I used in my PSFK example was generated using Google&#039;s advanced search page, i didnt have to remember it.

3. I was talking about IBM&#039;s Information Integrator in the context of Adventnet SQLOne type of approoach.  It allows you to create a federated query that runs across several information stores and bring back the information.

Interesting debate again.

</description>
		<content:encoded><![CDATA[<p>Ganesh,</p>
<p>Thanks for the comments.</p>
<p>1. Yes, you are right in the sense that WIMP will not die that easily and it should not because it does offer significant productivity improvements.</p>
<p>2. I am only arguing that Search could be a unifying metaphor for the various app silos in the Enterprise. Its not necessary that it has to be one button.  Therefore, when you use Onebox search, you can do simple searches and using Advanced Search you can do slightly more advanced searches. The search string I used in my PSFK example was generated using Google&#8217;s advanced search page, i didnt have to remember it.</p>
<p>3. I was talking about IBM&#8217;s Information Integrator in the context of Adventnet SQLOne type of approoach.  It allows you to create a federated query that runs across several information stores and bring back the information.</p>
<p>Interesting debate again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.sastwingees.org/2006/05/21/why-the-wimp-user-interface-is-dead-for-information-retrieval/comment-page-1/#comment-182</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 22 May 2006 05:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/2006/05/21/why-the-wimp-user-interface-is-dead-for-information-retrieval/#comment-182</guid>
		<description>Sukumar,

Perhaps, it is my fault - I take the word &quot;one box search&quot; literally and all my past comments (and this one too) is based on that. And anytime I hear any kind of thing becoming dead in the S/W industry, it always seems to come back in a different shape or form.

1. I almost agree that &quot;&lt;em&gt;all OLTP apps have become silos or islands of information or fiefdoms&lt;/em&gt;&quot;. I would just change &quot;all&quot; to &quot;almost all&quot;. I believe that with the evolution of SOA and mashups, end-users will have the ability to develop sit-apps by putting together services created by IT organizations. This would be one way to destruct the silos - exposing capabilities as services. UIs can be put together by end-users based on the services.

2. In the example, the minute I have to press the &quot;Advanced Search&quot; button, it is not &quot;one button search&quot; anymore!!  In the blogsearch example you gave, I certainly would not want to remember the syntax for the search string - &quot;inblogtitle:PSFK inpostauthor:Sukumar blogurl:http://www.psfk.com/&quot;. So, I would end up using the &quot;Advanced Search&quot; button. And I would certainly like a pointer device (mouse in this case) to navigate the text boxes in the &quot;Advanced Search&quot; window. I as software professional would not want to remember the syntax. So, in your example, I would certainly not expect the Order Entry Clerk or Financial Analyst remember the syntax for his/her search. I do agree that for _very basic_ searches, one-box could be the way to go.

3. I do not understand the relevance of &quot;one-box&quot; search with solutions such as IBM&#039;s &quot;Information Integrator&quot;. This like lots of their software is a middleware that lets one aggregate/integrate data (both structured and unstructured) across multiple-disparate repositories. It provides a way to unify data and let a single search gather data from the various repositories.  The UI/veneer for these searches could be anything - one-box or not.

Ganesh

</description>
		<content:encoded><![CDATA[<p>Sukumar,</p>
<p>Perhaps, it is my fault &#8211; I take the word &#8220;one box search&#8221; literally and all my past comments (and this one too) is based on that. And anytime I hear any kind of thing becoming dead in the S/W industry, it always seems to come back in a different shape or form.</p>
<p>1. I almost agree that &#8220;<em>all OLTP apps have become silos or islands of information or fiefdoms</em>&#8220;. I would just change &#8220;all&#8221; to &#8220;almost all&#8221;. I believe that with the evolution of SOA and mashups, end-users will have the ability to develop sit-apps by putting together services created by IT organizations. This would be one way to destruct the silos &#8211; exposing capabilities as services. UIs can be put together by end-users based on the services.</p>
<p>2. In the example, the minute I have to press the &#8220;Advanced Search&#8221; button, it is not &#8220;one button search&#8221; anymore!!  In the blogsearch example you gave, I certainly would not want to remember the syntax for the search string &#8211; &#8220;inblogtitle:PSFK inpostauthor:Sukumar blogurl:http://www.psfk.com/&#8221;. So, I would end up using the &#8220;Advanced Search&#8221; button. And I would certainly like a pointer device (mouse in this case) to navigate the text boxes in the &#8220;Advanced Search&#8221; window. I as software professional would not want to remember the syntax. So, in your example, I would certainly not expect the Order Entry Clerk or Financial Analyst remember the syntax for his/her search. I do agree that for _very basic_ searches, one-box could be the way to go.</p>
<p>3. I do not understand the relevance of &#8220;one-box&#8221; search with solutions such as IBM&#8217;s &#8220;Information Integrator&#8221;. This like lots of their software is a middleware that lets one aggregate/integrate data (both structured and unstructured) across multiple-disparate repositories. It provides a way to unify data and let a single search gather data from the various repositories.  The UI/veneer for these searches could be anything &#8211; one-box or not.</p>
<p>Ganesh</p>
]]></content:encoded>
	</item>
</channel>
</rss>
