874
edits
Labs/Ubiquity/0.2 Design: UI and Security Extensibility: Difference between revisions
Labs/Ubiquity/0.2 Design: UI and Security Extensibility (view source)
Revision as of 01:54, 16 December 2008
, 16 December 2008added ui extensibility section
(origination) |
(added ui extensibility section) |
||
| Line 10: | Line 10: | ||
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. | 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 to understand the [[Labs/Ubiquity/Ubiquity_0.1.3_Architecture|Ubiquity 0.1.3 Architecture]]. | 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 == | == 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 == | == Security Extensibility == | ||