The calendar provider has and will change, often significantly, between platform releases. And I would be willing to bet that some device manufacturers have changed it for their own use. You just can't on whatever you figure out to work on one device to work on other devices.
Re: "undocumented" and "private" -- if something is not documented, it is not part of the SDK, and NOT FOR APPS TO USE. There is no need to play terminology games about this, we have been very clear from day one that this is how we do things on Android. Further, I will ask that you move this discussion off android-developers, since android-developers is for discussions about using the SDK, and the calendar provider is not part of the SDK. On Fri, Feb 25, 2011 at 6:51 AM, Marcin Orlowski <[email protected]>wrote: > > Anyone needing to ask questions about an undocumented, unsupported API > should not be using it. > > Calendar is not part of SDK as such situation lets Google change > whatever they want and to not bother the others, but I dare to point > that there significiant difference between "undocumented" and > "private" (restricted). Calendar Provider is "undocumented". > > > Search for Google Calendar GData API. > > Which besides being more official than Calendar Provider requires data > connection. > > > You are cordially invited to add me to your email filters, then, so > > that you don't have to read any more of my messages. > > It seems you took it too personally, for no reason. > > > Somebody with the itch to scratch should be creating their own > > compatibility layer atop such undocumented, unsupported APIs. In the > > case of the Calendar, such a compatibility layer: > [...] > > The same holds true for just about any other undocumented, unsupported > > API in Android. I haven't had the itch, so I have not scratched it. If > > somebody comes up with such a compatibility layer, I will be happy to > > point people in that direction. > > Do agree, but to my knowledge no such layer exists and if TK or anyone > else is going to write such, he still may need the answers, isn't it? > We are now falling into academic debate, which imho is of no real > benefit. If I remember correctly we got 44k devs here so definitely > one knows the answers. > > -- > Regards, > Marcin > > -- > 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 > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
