- From: Bjartur Thorlacius <svartman95@gmail.com>
- Date: Thu, 19 Jan 2012 10:27:56 +0000
- To: Paul Kinlan <paulkinlan@google.com>
- Cc: Giuseppe Pascale <giuseppep@opera.com>, WebIntents <public-web-intents@w3.org>
On 1/19/12, Paul Kinlan <paulkinlan@google.com> wrote: > I am sorry but I am having a really hard time understanding what you > are stating in the last two paragraphs > Yeah, I had a really hard time wording them comprehensibly and grammatically correctly. Pardon my English. > Are you saying that invocation of an intent should not have to be > scripted? For example in the case of <input type="file" > accepts="image/*" /> should delegate to the intent system allowing the > user to choose a file from the file system or their preferred service? > And the browser should be able to "insert" actions in to a context > menu? > Yes. Well, ideally preferred services would form a part of the filesystem, but that's an implementation detail. My point is simply that the use cases for the client API are much fewer than those for the service API. In fact, I've only found one use case for the client API. > The former, I wish to see, the later in Chrome's case in the short > term can be handled by extensions, and in fact I have the extensions > ready in the github repository. > Great!
Received on Thursday, 19 January 2012 10:28:28 UTC