Re: Allow ... centralized dialog up front

2013-02-02 Thread Florian Bösch
I do not particularly care what research you will find to support the UI-flow that the existence of a requestAPIs API will eventually give rise to. I do say simply this, the research presented, and pretty much common sense as well easily shows that the current course is foolhardy and ungainy on

Re: Allow ... centralized dialog up front

2013-02-02 Thread Keean Schupke
I would like the permissions to be changeable. Not a one time dialog that appears and irrevocably commits me to my choices, but a page with enable/disable toggles I can return and review the permissions and change at any time. How about instead of a request API the required permissions are in

Re: Allow ... centralized dialog up front

2013-02-02 Thread Florian Bösch
I thought this was obvious but maybe not. Of course I had in mind that: - A user gets some centralized place to manage his sites - He can change permissions - If the sites preferences change, the permissions pop up again. - Some way for the user to re-engage the permission dialog for the site

Re: Allow ... centralized dialog up front

2013-02-02 Thread Florian Bösch
On Sat, Feb 2, 2013 at 11:16 AM, Keean Schupke ke...@fry-it.com wrote: I think a static declaration is better for security, so if a permission is not there I don't think it should be allowed to request it later. Of course how this is presented to the user is entirely separate, an the UI could

Re: Allow ... centralized dialog up front

2013-02-02 Thread Keean Schupke
There are benefits to the user, in that it allows all permissions to be managed from one place. I am not sure I like the idea of making the popups an application thing. I think it should be decided by the browser. In any case you would still need the ...Allow callbacks as the user may have gone

Re: Allow ... centralized dialog up front

2013-02-02 Thread Florian Bösch
And you can have the *the* callback (singular, centralized) as onAPIPermissionChange just fine. If you want to improve things for the user and the developer, you can't go with a solution that doesn't make it any easier for the developer. Your solution will be ignored, nay ridiculed. If you want

Re: Allow ... centralized dialog up front

2013-02-02 Thread Keean Schupke
I didn't think of that. The app would have to maintain its own set of permission flags updated by the callback. I am not sure that's easier than just chaining an anonymous function... But I guess that's a programming style issue. Cheers, Keean. On 2 Feb 2013 10:47, Florian Bösch pya...@gmail.com

Re: Allow ... centralized dialog up front

2013-02-02 Thread Florian Bösch
Usually games (especially 3D applications) would like to get capabilities that they can use out of the way up front so they don't have to care about it later on. On Sat, Feb 2, 2013 at 11:59 AM, Keean Schupke ke...@fry-it.com wrote: I didn't think of that. The app would have to maintain its