This module is currently built for Drupal 4.7 (ouch), and requires a huge update of the API to the new GData API, which now uses the Zend Framework. There are a number of things we'll have to do in order to achieve this:
- 1. The Zend Framework
- Since the GData API is part of the Zend Framework, we'll have to make this module require the installation of the Zend Framework. Since the Zend Framework is another API, it would make sense to abstract this out of GData and have a new module to manage the proper installation of it. So, I created a new Zend Framework module. The GData Drupal module will have to depend on it.
- 2. Architecture
- Since the GData API can do so much, we have to re-evaluate the design structure of the GData module.
- GData Module: Base module to ensure that the GData API is available, as well as provide some configuration options
- GData Service/Server: Instead of providing its own hook, it might be worth investigating the Services module to communicate with a large amount of modules and protocols. This would turn GData into a web service server to provide a way of communicating GData information instead of its own module/hook.
- 3. Sample Module
- Create a simple module that would use the GData module. Maybe retrieve a list of published Google documents? Get analytics information about your Drupal website? Perform an AJAX search on of code on Google Code?
Comments
Comment #1
Anonymous (not verified) commentedRob,
Please see my issue here: http://drupal.org/node/237238 requesting maintainership.
These are some of the issues that you've mentioned above that I'd like to tackle. I need the gdata api for a site I am currently developing, and would like to take this over rather than rolling my own and not contributing it.
Comment #2
Anonymous (not verified) commentedRob,
These are all great ideas. I'd like to work with you and the rest of the community to figure out what all we want to do with this module now that I've taken over maintainership.
Looking at the existing code, I feel that it's going about integration in the wrong way, and I'll be scraping most if not all of it. Additionally, this is 4.7.x code, and my target here is 6.x and HEAD.
Comment #3
robloachSounds great! Is this for Summer of Code?
Comment #4
Anonymous (not verified) commentedNah, I'm not a student, I'm past that time :)
Comment #5
robloachThere are some projects that are similar to what's mentioned here though. And you could be a mentor ;-) .
Comment #6
flickerfly commentedRob, thanks for tackling this. I'm looking forward to testing it. :-)
Comment #7
ericduran commentedHi,
I am curious as to what is the status of this?
I have time to work on this. Is there a discussion regarding this module anywhere?
Comment #8
robloachI was going to be working on this for a client, and unfortunately I'm not working on that project anymore.... I'd love to do any testing if anyone gives it a shot....
Comment #9
ericduran commentedok. Well I integrated provisioning for 5.x for a pass client. But I never put it on drupal.org. I starter working on one for 6.x and I put it off but now I need it for a separate client. I'm currently using the zend module you created. That way It can save me from doing all the zend checking and loading.
We'll I'll put it up when I'm done. Is a completely separate provisioning module but hopefully it can be integrated with this Gdata module in the feature.
When I'm done with the provisioning I don't mind taking this on. Is no one is doing it by then.
Comment #10
ckngAny updates on this?
Comment #11
vacilando commentedSubscribing
Comment #12
msumme commentedWho's heading up this project?
I'm currently just modifying the atom feed module to have a google base feed for a certain content type, but that's not really the best way to go about doing something like this...
How much work needs to be done? Are there any current contributors?
This is definitely something I'd be interested in contributing to.
Comment #13
socialnicheguru commentedsubscribing