Closed Bug 335826 Opened 19 years ago Closed 17 years ago

Support for Google Data API

Categories

(Calendar :: Provider: GData, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: JasnaPaka, Assigned: Fallen)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060428 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060428 Minefield/3.0a1 It would be nice to see support for Google Calendar through Google Data API. http://code.google.com/apis/gdata/index.html Reproducible: Always
One thing we still need to do still is decide how we want to evaluate what set of providers should live in the tree, be on by default, etc. That probably won't happen until we get a little further along with the product definition story.
I personaly don't think this should go into the tree, but should rather be made availible by an extension.
Severity: normal → enhancement
garyvdm: Just curious what the status of this might be. I got the impression you were coming along on it?
I am working on this, feel free to assign to me if you have editbugs privs. The following is working atm: * Login via ClientLogin (100%) * parsing of XML feed to calIEvent (80%) * parsing of calIEvent to XML entry (60%) Probably some other things I forgot.
Assignee: nobody → bugzilla
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Depends on: 355117
This Bug describes full support of the Google Calendar Data API. I will close it when all parts are added.
No longer depends on: 355117
Depends on: 355226
Depends on: 355117
Depends on: 362645
Depends on: 362648
Depends on: 362650
Depends on: 362653
Component: General → Provider: GData
QA Contact: general → gdata-provider
What relationship does this have with bug #355117, which appears to have been fixed on trunk as of 1 MARCH 2007?
This bug used to be the tracking bug to easier find all gdata bugs. Now that there is a component for the gdata provider, there is no need to keep this bug open. -> INVALID
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.