Lasse, I think your includes look normal. You are using two APIs to run your app so it makes sense to load Gdata_Docs and Gdata_Spreadsheets. The proxy adapter should not be needed twice. I am not sure what the reason is for modifying the Zend_Gdata_Doc's classes constructor. I am not 100% sure what you mean with specifying the http://google.com:443 address. The Zend_Http_Client_Adapter_Proxy lives outside of the Zend_Gdata package so it has to work generically for all addresses.
You can't programmatically modify sharing information for Google Documents (and Spreadsheets) just yet. We are actively working on this feature request and should have something ready soon but I can't disclose exact dates. It seems like your use-case requires you to create the spreadsheet, programmatically populate the data and then give a user access to it. For this you will need the programmatic ACL modification which is being worked on. Please star the feature request linked here to be notified when it is implemented: http://code.google.com/p/gdata-issues/issues/detail?id=311 There also another enhancement that we are looking into, which is to allow for programmatic export of Documents in various format. This would allow your application to download a binary .xls file which you can then just email to your users: http://code.google.com/p/gdata-issues/issues/detail?id=70 If you can't wait and need to get around this, you could just save the data in your client app and then programmatically generate a csv file or something on your end which you can email out. Let me know if this answers your questions Thanks - Jochen On Sep 16, 12:39 am, Lasse <[EMAIL PROTECTED]> wrote: > Hi, > Thanx for your answer :) > I replaced my include with: > require_once 'Zend/Loader.php'; > Zend_Loader::loadClass('Zend_Gdata'); > Zend_Loader::loadClass('Zend_Gdata_ClientLogin'); > Zend_Loader::loadClass('Zend_Gdata_Docs'); > Zend_Loader::loadClass('Zend_Gdata_Spreadsheets'); > Zend_Loader::loadClass('Zend_Http_Client'); > which I found in an example, it probably does the INCLUDE in a more > complex way, but what the hey. > > Things I do NOT like with my example: > 1. I have to modify Zend_Gdata_Doc to make the proxy work. I specify > the proxy in my code but that is not enough I also have to modify > Zend_Gdata_Doc which I do not like. I think creating the instance > > $client = new Zend_Http_Client('http://www.google.com:443', $config); > > should also save my proxy definition, but it does not! > > 2. Since I have to define the proxy I have to explicitly define the > addresshttp://www.google.com:443. It would have been better if I > could have used the default value as in your example. > > This is for a data warehouse application. I produce reports and send > them to users I not necessarily know up front. It might be sensitive > material, so it is not for anyone with access to Google docs. So I > want to send the physical report in the mail, like you normally do > with Excel reports. If this is not possible, maybe I have to limit > recipients to GDocs users. > > I also would like to know where the speadshhet is stored. E.g. if the > user is a registred user in China, will the spreadsheet be stored in a > server in China? If this is the case I maybe can turn this into an > advantage, using my China user credentials I could create reports in > Sweden and storing them in the vincinity of China, and thereby giving > my Chinese user 'local' access to the spreadsheet. If this really is > an advantage I do not know, but the concept is really cool. Cloud > computing wow :)) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Docs Data APIs" 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-Docs-Data-APIs?hl=en -~----------~----~----~----~------~----~------~--~---
