Page source:

<H1>WubHub Ideas</H1>

This page maintains a prioritized (top = most important in each category) wish-list for WubHub.  WubHub Members, please edit the page to add your thoughts.  Developers, feel free to contribute implementations for ideas on this page!

<h2>Specific ideas</h2>

<h3>WubHub Commands</h3>
<UL>
   <LI> movies out this week -> list, with "imdb" and "add to netflix queue" button
   <LI> Restaurant search (OpenTable).
   <LI> Notify person command, that can be used in conjunction with others, such as map(restaurants(italian)) > girish
   <LI> Tutorial Page
   <LI> Survey & Voting
   <LI> Some functions may require too many arguments (such as reserving a plane ticket). Maybe the commands syntax should allow for named arguments (e.g. expedia(arrival="sfo", destination="sjc", date="12/22/2005", maxPrice="300")). This way, providing values for all arguments can be made optional and maybe a more interactive interface can be used to ask for mandatory arguments. 
   <LI> Add XML (or soap) API to commands.
   <LI> A command to search for available commands based on command name or description (as there may be too many global commands)
   <LI> comment(page): Be able to add comments on any page (or subpage)?  Useful for blogs, etc.
</UL>


<h3>User Interface</h3>
<UL>
   <LI> Portlet interface that lets you combine results from multiple commands on a single page [in progress, see ajaxGroup.ajaxGroup]
   <LI> More support for wubvars as a scratchpad, where you can store results and
           then chain commands together
   <LI> Use AJAX to allow typing in the shortest possible command and autocompleting
   <LI> Make CSS files WubHub data pages so communities can edit look/feel [Adam]
   <LI> How to leverage tools like Konfabulator or Laszlo -> WebHub as widget factory [David]
   <LI> Better home page: multiple columns, portlets, etc. [Ken Nitz] -- in progress, see ajaxGroup.ajaxGroup
   <LI> Automatically list user's top five commands on home page [Girish]
</UL>

<h3>WubHub Environment</h3>
<UL>
   <LI> Change Render function for viewing source code so that functions are clickable.  Clicking on a function shows user that function's definition.
   <LI> Interactive debugging
   <LI> Type system (microformats), with associated renderers
   <LI> Mandatory, optional, hidden parameters to functions
   <LI> Allow "_" character in identifiers
   <LI> Use WebL timers to schedule commands [Didier]
   <LI> New page type: WSDL (automatically interfaces with SOAP) [John]
   <LI> Versioning [David]
   <LI> API layer open to external calls [David]
   <LI> Add notion of "current directory" to path mechanism [Adam]
   <LI> Make types community sharable, documentable, searchable
</UL>

<h3>Miscellaneous</h3>
<UL>
   <LI> RSS Reader
   <LI> Local instance of WubHub (for integration of desktop sources) that is extended by WubHub.com (for collaboration)
   <LI> Plugin toolbar for IE/Firefox
   <LI> Target some domain, and set of users.  What domains?
   <LI> Prearranged/programmable structural elements, i.e. as seen on backpackit.com, or Google Store.
</UL>

<h3>Bugs</h3>
<UL>
  <LI> Remove edit links (add view ones instead?) for pages when user does not have edit permission on ls command, "Source:" link etc.
  <LI> The edit link on a command that has a render function edits the render function and not the command itself.  This is particularly confusing when a user doesn't have permission to edit the render function, but does have permission to edit the function itself. [bear]
  <LI> Error handling could be improved.
</UL>


<h2>"Big picture" ideas</h2>

<h3>New platform directions</h3>
<ul>
  <li> Client-end execution (scales better, fewer abuse incentives) - using applets?
  <li> Support more langauges -- perhaps other scripting languages on Java platform:
       Javascript (Rhino), JRuby, Jython, ... -- in progress for Javascript
  <li> XPath and DOM support
</ul>

<h2>Some ideas that have been implemented</h2>

   <LI> Single signon vault

...