Good that you mention, I was contemplating writing an email about exactly this. I am very much for fixing bugs. I think the basic functionality of the gCal API exists, allowing many different applications to work with Google Calendar.
A lot of the bugs discussed on this list have not been fixed yet. Don't understand this as a gripe, just as my opinion that it is more important to have a working API than to have many new features implemented. Specifically what I think is most severe right now is the fact that a one day all day event gets parsed into a two-day event. (See http://code.google.com/p/google-gdata/issues/detail?id=19 ) The next item in priority would then be new features. I would enjoy having a to-do list feature, but I understand there are other features that are more important. For example being able to create calendars via API or extending the meta-feed to have more information, or adding information from the metafeed (namely timezone) to the event feed. Documentation is fairly good. There might be some things that are not at its best, but with the new knowledge base and the newsgroup there should be enough information for most everyone. Support is great! This is a good moment to thank Ryan and Frank and the others for their great dedication on this newsgroup. All of my questions have had a quick response, mostly with a fitting answer that helped me solve my problem very quickly. You guys are great! Philipp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
