Difference between revisions of "Documentation/DevGuide/OfficeDev/Command URL"
OOoWikiBot (talk | contribs) m (Robot: Changing Category:Documentation/Developers Guide/Office Development) |
|||
| Line 10: | Line 10: | ||
In the dispatch framework, every possible user action is defined as an executable ''command'', and every possible visualization as a reflection of something that is exposed by the component is defined as an ''attribute''. Every executable command and every attribute is a feature of the office component, and the dispatch framework gives every feature a name called ''command URL''. It is represented by a <idl>com.sun.star.util.URL</idl> struct. | In the dispatch framework, every possible user action is defined as an executable ''command'', and every possible visualization as a reflection of something that is exposed by the component is defined as an ''attribute''. Every executable command and every attribute is a feature of the office component, and the dispatch framework gives every feature a name called ''command URL''. It is represented by a <idl>com.sun.star.util.URL</idl> struct. | ||
| − | Command URLs are strings that follow the ''protocol_scheme:protocol_specific_part'' pattern. Public URL schemes, such as ''file:'' or ''http'' can be used here.Executing a request with a URL that points to a location of a document means that this document is loaded. In general, both parts of the command URL can be arbitrary strings, but a request cannot be executed if there is an object that does not know how to handle its command URL. | + | Command URLs are strings that follow the ''protocol_scheme:protocol_specific_part'' pattern. Public URL schemes, such as ''file:'' or ''http'' can be used here. Executing a request with a URL that points to a location of a document means that this document is loaded. In general, both parts of the command URL can be arbitrary strings, but a request cannot be executed if there is an object that does not know how to handle its command URL. |
{{PDL1}} | {{PDL1}} | ||
[[Category:Documentation/Developer's Guide/Office Development]] | [[Category:Documentation/Developer's Guide/Office Development]] | ||
Revision as of 19:16, 4 October 2008
In the dispatch framework, every possible user action is defined as an executable command, and every possible visualization as a reflection of something that is exposed by the component is defined as an attribute. Every executable command and every attribute is a feature of the office component, and the dispatch framework gives every feature a name called command URL. It is represented by a com.sun.star.util.URL struct.
Command URLs are strings that follow the protocol_scheme:protocol_specific_part pattern. Public URL schemes, such as file: or http can be used here. Executing a request with a URL that points to a location of a document means that this document is loaded. In general, both parts of the command URL can be arbitrary strings, but a request cannot be executed if there is an object that does not know how to handle its command URL.
| Content on this page is licensed under the Public Documentation License (PDL). |
