On Sat, Jan 8, 2011 at 1:16 AM, Bob Kerns <[email protected]> wrote: > But you'll note that my suggested minimal protocol side-steps the > issue by not exposing anything about the email other than its arrival, > except via an optional content provider URL. That's where the > permissions would hook in.
Off the cuff, I'd want the permissions even on the broadcasts, but that might just be me. > What you propose below is another approach to this -- unifying > applications in the face of non-standardization. It has its merits, > especially as a transitional measure. It is also an opportunity to > establish a defacto standard, especially if it publishes the best > protocol as an OpenIntents.org interface, and supports that well. New > apps (or old) which want to integrate well, could implement that > protocol. Nowadays, I run in that direction under the "my arms are too short to box with Google" mindset I'm sporting. > But a bit of leadership from Google would really help here. For > example -- one VERY easy thing that the Google team could do is to > publicize OpenIntents.org here: > > http://developer.android.com/intl/de/resources/community-groups.html I've been lobbying for this since 2008. If I can't convince them to put a frakkin' hyperlink on a Web page, there's no way in hell that I'm going to convince them to standardize APIs for calendar, email, etc. As I said, "my arms are too short to box with Google". That's why I see the only hope in being a community-led approach: -- Create an API (e.g., email) -- Convince third-party app developers (e.g., K9) to implement said API, probably by helping them design the API in the first place -- Create a wrapper that uses all sorts of nasty techniques to graft that API on top of what's in Android today (e.g., Email app, device-specific email clients) -- Pray for a groundswell of apps using said API -- Much later, after this stuff becomes popular, try to contribute patches back to AOSP to put the API officially on this stuff, so we can get rid of (or at least shrink) the wrapper However, the kernel of all that is somebody with the itch to scratch. Right now, I don't have the itch to standardize email, calendar, etc. APIs. At most, I have the meta-itch of figuring out a process by which we can collectively get stuff like that done. I'm with you, in that I think Android is a more powerful platform with these sorts of things in place. However, my plate overfloweth, and I have lots of windmills to tilt at, to mix metaphors. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.4 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
