- From: Paul Kinlan <paulkinlan@google.com>
- Date: Tue, 6 Mar 2012 10:59:20 +0000
- To: Thomas Steiner <tomac@google.com>
- Cc: James Hawkins <jhawkins@google.com>, WebIntents <public-web-intents@w3.org>
Just to add my 2 pennies.
+1 for optional extra, but I quite like C.... B should just disappear :)
To be devils advocate though: An extra optional dictionary appears
after an option data parameter. So for the pick intent in particular,
we will have `new Intent("http://webintents.org/", "image/*",
undefined, {.....}), with this model we can't sanely introduce another
mandatory argument, everything is now optional in the constructor.
Extras need to also be on the return in postResult (again for pick and
other intents)
On Tue, Mar 6, 2012 at 8:18 AM, Thomas Steiner <tomac@google.com> wrote:
>
> +1 to an optional extras parameter (option A)
>
> --Tom
>
> --
> Thomas Steiner, Research Scientist, Google Inc.
> http://blog.tomayac.com, http://twitter.com/tomayac
>
--
Paul Kinlan
Developer Advocate @ Google for Chrome and HTML5
G+: http://plus.ly/paul.kinlan
t: +447730517944
tw: @Paul_Kinlan
LinkedIn: http://uk.linkedin.com/in/paulkinlan
Blog: http://paul.kinlan.me
Skype: paul.kinlan
Received on Tuesday, 6 March 2012 10:59:50 UTC