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 Thread level granularity then some form of either providing the widget with a Canvas or using IPC calls back from the widget are the only way to go. Al. Romain Guy wrote: > > 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 9:12 AM, "Al Sutton" <a...@funkyandroid.com >> <mailto:a...@funkyandroid.com>> wrote: >> >> >> 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... >> > > > -- * Written an Android App? - List it at http://andappstore.com/ * ====== Funky Android Limited is registered in England & Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
