WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
On Tue, Feb 21, 2012 at 11:31 AM, Bjartur Thorlacius
> Þann þri 21.feb 2012 18:44, skrifaði James Hawkins:
>> I'm not sure if the proposal was explicit enough, but for the RPH-esque
>> functionality in Web Intents, we activate WI in the same circumstances
>> RPH is activated, which is when links are activated in a page. Can you
>> elucidate how the scenarios you listed could be handled? Note these
>> scenarios are above and beyond RPH, but we're not trying to make the API
> Windows Explorer (the file manager) does for example offer users to edit
> images upon right-click. I worry that if URI scheme handlers need not only
> take care of fetching but also of presentation, other actions than view will
> be unnecessarily hard to implement. Thus I figure retrieval and presentation
> must be separated.
> (view (fetch uniform:resource/locator))
> (edit (fetch uniform:resource/locator))
> instead of
> (fetch-and-view uniform:resource/locator)
Is this use case not fully handled by the UA specifying the
appropriate action when building the intent, e.g., the user
right-clicks on an image in a page and the UA constructs context menu
items for edit/share/etc. action?