WebAPI/WebActivities: Difference between revisions
< WebAPI
Jump to navigation
Jump to search
m (→Proposed API) |
m (→Introduction) |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
Web Activities is a counter-proposal to Web Intents. It is trying to | Web Activities is a counter-proposal to Web Intents. It is trying to limit the scope of the API to the following use case: ''APP A wants to delegate an activity to APP B''. Web Activities isn't a discovery API or a communication API. Those things happen in the background and are completely transparent to the caller. | ||
== Proposed API == | == Proposed API == | ||
Revision as of 17:17, 30 May 2012
Introduction
Web Activities is a counter-proposal to Web Intents. It is trying to limit the scope of the API to the following use case: APP A wants to delegate an activity to APP B. Web Activities isn't a discovery API or a communication API. Those things happen in the background and are completely transparent to the caller.
Proposed API
interface ActivityOptions {
attribute DOMString name;
attribute Object? data; // a dictionary
};
[Constructor(DOMString name)]
interface ActivityHandlerDescription {
attribute DOMString name; // default has to be passed to ctor
attribute DOMString href; // default is current location
attribute DOMString disposition; // going to be an enum with a default
attribute boolean returnValue;
attribute Object? filters; // a dictionary
};
interface ActivityRequestHandler {
void postResult(any result);
void postError(DOMString error);
readonly attribute ActivityOptions source;
};
[Constructor(ActivityOptions options)]
interface Activity : DOMRequest {
};
partial interface Navigator {
DOMRequest registerActivityHandler(ActivityDescription d);
void unregisterActivityHandler(ActivityDescription d);
bool isActivityHandlerRegistered(ActivityHandler handler);
};