874
edits
Labs/Ubiquity/0.2 Design: UI and Security Extensibility: Difference between revisions
Jump to navigation
Jump to search
Labs/Ubiquity/0.2 Design: UI and Security Extensibility (view source)
Revision as of 19:24, 16 December 2008
, 16 December 2008Framed UI extensibility in terms of the architectural diagram
(Changed to architecture proposal 2) |
(Framed UI extensibility in terms of the architectural diagram) |
||
| Line 20: | Line 20: | ||
== UI Extensibility == | == UI Extensibility == | ||
Given a selection, | All UI components will interact with the '''UI Manager''' depicted in the proposed architectural diagram, which essentially serves as a [http://en.wikipedia.org/wiki/Facade_pattern facade] to Ubiquity's functionality. | ||
Given a selection, clients of the UI Manager 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". | * 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". | ||
| Line 28: | Line 30: | ||
:::''Implementation note: Look at <tt>CommandSource</tt>'s method to get all commands.'' | :::''Implementation note: Look at <tt>CommandSource</tt>'s method to get all commands.'' | ||
Given a command, | Given a command, clients of the UI Manager should be able to: | ||
* Figure out what objects the command takes. | * Figure out what objects the command takes. | ||