I managed to get Google Spreadsheets and Google App Engine to work, coding in Python. But it has been a nightmare and I would need to see some serious improvement worked out before I consider doing it again.
The lack of examples really made it more of a struggle than it needed to be. It probably didn't helpt that I've only ever written web architecture using idiosyncratic in-house libraries in Java in the past, but considering how easy it was to get a Google App Engine server up and running, it was a real surprise to see just how hard it was to use the Spreadsheets API. The real killer was authentication. There a lack of python examples really caused things to grind to a halt. There was also a lot of confusion as to which version of the libraries a Python developer should use. Version 1 was the only documented one, yet its use was actively discouraged in some of the documentation. Based on my experience, I'd recommend trying .Net or Java. The documentation for them seems more consistent across all the APIs. Until there's a working example of OAuth2 authentication in Python with the Version 3 libraries, I'd caution against it. Tom On Saturday, March 31, 2012 8:25:15 PM UTC+1, niraj wrote: > > The whole thing about using Google App Engine is a joke. > > I tried Google App Engine with Google Spreadsheets. could never get it to > work. > Reasons: > 1. The documentation on using AppEngine with the API mess between gdata > and googl-client-api *Really* sucks. > 2. The Google Client API does not given samples for spreadsheets. Leaves > it at a generic comment of use ATOM. > 3. I tried to dig up into the mercurial to find a relevant example. Google > has a link hell in there. Links pointing to old stuff etc. > 4. I still have not found a good example that explains the use of OAuth2 > with AppEngine and Google Docs. > > Recommendation : > 1. Use Gdata api > 2. Use on Amazon. > > > > > On Friday, March 30, 2012 6:06:24 PM UTC-7, Andrew Malcolmson wrote: >> >> If you use Python, Java, or Go, you can also program Google App Engine. >> Personally I use Python. > >
