<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://dashes.com/anil/2003/01/taskspecific-br.html" />
  <link rel="self" type="application/atom+xml" href="http://dashes.com/anil/atom.xml" />
  <id>tag:dashes.com,2009:/anil//1/tag:www.dashes.com,2003:/anil//1.1586-</id>
  <updated></updated>
  <title>Comments for task-specific browser UIs</title>
  <subtitle>A Blog About Making Culture</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.3-en</generator>
  <entry>
    <id>tag:www.dashes.com,2003:/anil//1.1586</id>
    <link rel="alternate" type="text/html" href="http://dashes.com/anil/2003/01/taskspecific-br.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://dashes.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=1586" title="task-specific browser UIs" />
    <published>2003-01-10T07:08:07Z</published>
    <updated>2005-08-12T06:49:43Z</updated>
    <title>task-specific browser UIs</title>
    <summary><![CDATA[When Jason asked &quot;Why are Safari and Sherlock two different applications?&quot; it made me realize that what I want is a desktop application, similar to...]]></summary>
    <author>
      <name>Anil</name>
      <uri>http://anildash.com/</uri>
    </author>
    
    <category term="tech" />
    
    <content type="html" xml:lang="en" xml:base="http://dashes.com/anil/">
      <![CDATA[<p>When Jason asked &quot;<a title="Why are Safari and Sherlock two different applications? (kottke.org)" href="http://www.kottke.org/03/01/030108why_are_safa.html">Why are Safari and Sherlock two different applications?</a>&quot; it made me realize that what I want is a desktop application, similar to Andre's <a href="http://www.torrez.net/archives/xmlrpc_request_builder.php">Konstructor</a>, that understands SOAP as well as XML-RPC and can query a WSDL file to find out what kinds of input the web service requires.</p>
<p>Then, based on the type of input requested, it would display the appropriate widgets (checkboxes for true/false, drop-downs for selection lists) and arrange them on a form according to an editable set of rules. The end results wouldn't be pretty, but you might end up with a bunch of applications that assemble themselves around web services.</p>
<p>If you could write the whole thing in XUL/javascript, it could run within any Mozilla-based browser.</p>]]>
      
    </content>
  </entry>

</feed>