Plus you have cross scripting accross domains can of worms as well..
Its one reason why even if I am embedding most of my app in web code
via webview I am still using native side to
do the app password and OAUTH permissions at start up to void such
can of worms
On Feb 24, 12:07 pm, Dianne H
On Tue, Feb 24, 2009 at 7:47 AM, Al Sutton wrote:
> Just to go a bit further on this, I'd hope you'd be implementing at
> least a subset of http://desktop.google.com/plugins/
> It's Google code, it'd bring a lot of widgets/gadgets onto Android in a
> short time frame, and would lessen the learnin
I'm starting to see the can of worms. I'd assumed there was already
something in place for handling permission separation and that access
was locked down, I hadn't realised that the current home widgets were so
tightly integrated.
I'm guessing unless the permission model can be brought down to
Isn't that something that's already solved with the application
permissions system and the cross cuts into the framework code which
support it?
Romain Guy wrote:
> That doesn't make it easy to do. The main issue is security.
>
> On Tue, Feb 24, 2009 at 7:38 AM, Al Sutton wrote:
>
>> That's
No, that's the point. You don't want to run foreign code (the widget) in
Home because it would then be able to use Home's multiple permissions. There
are several approaches to solve this. One is to rely on remote views, like
in the status bar, but it limits what the widgets can do.
On Feb 24, 2009
Because it's a hard problem.
JBQ
On Mon, Feb 23, 2009 at 11:00 PM, quill wrote:
>
> Hi, anyone who knows why? If I want to do this, is it extensive? Only
> change the code in launcher in sdk?
> >
>
--
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.
Please don't contact me directly.
That doesn't make it easy to do. The main issue is security.
On Tue, Feb 24, 2009 at 7:38 AM, Al Sutton wrote:
>
> That's been solved many times before on other platforms.
>
> Al.
>
> Jean-Baptiste Queru wrote:
>> Because it's a hard problem.
>>
>> JBQ
>>
>> On Mon, Feb 23, 2009 at 11:00 PM, qui
Just to go a bit further on this, I'd hope you'd be implementing at
least a subset of http://desktop.google.com/plugins/
It's Google code, it'd bring a lot of widgets/gadgets onto Android in a
short time frame, and would lessen the learning curve for many people.
Al.
Al Sutton wrote:
> That's
That's been solved many times before on other platforms.
Al.
Jean-Baptiste Queru wrote:
> Because it's a hard problem.
>
> JBQ
>
> On Mon, Feb 23, 2009 at 11:00 PM, quill wrote:
>
>> Hi, anyone who knows why? If I want to do this, is it extensive? Only
>> change the code in launcher in sdk?
9 matches
Mail list logo
