874
edits
Changes
added ui extensibility section
Both of these solutions invite community members to create and implement new ideas to further the conversation about using the browser to connect web services together in a safe, humane way.
Before reading the rest of this document, it may be helpful for readers to understand the [[Labs/Ubiquity/Ubiquity_0.1.3_Architecture|Ubiquity 0.1.3 Architecture]].
== UI Extensibility ==
Given a selection, I should be able to:
* Determine what commands are apropos to operate on it. For instance, if I select a street address, one of the first commands that it matches should be "map".
:::''Implementation note: Look at the <tt>CommandManager</tt>'s noun-first-suggestions code.''
* Get a list of ''all'' commands that can apply to the selection.
:::''Implementation note: Look at <tt>CommandSource</tt>'s method to get all commands.''
Given a command, I should be able to:
* Figure out what objects the command takes.
:::''Implementation note: Once we [http://groups.google.com/group/ubiquity-core/browse_thread/thread/f7d8abf58724256 unify Verbs and Commands], this will be trivial.''
* Call the command.
:::''Implementation note: see above.''
== Security Extensibility ==