Tue May 10 18:54:00 CEST 2011
As a reminder: Do check the Google IO website for a live stream: www.google.com/io
Impression:
At 8:30 there were a lot of people ready to go in to the keynote room. There is a lot of buzz on what this year's IO might bring. Buzz ranging from hard core devs waiting for this or that new feature in Android or AppEngine to a more general buzz about the anticipated goodies.
KeyNote notes:
Tue May 10 02:13:00 CEST 2011
Ok, so I kind of neglected this blog a bit over the past few months... but we're back! Arrived in SF today to attend the Google IO conference 2011. News is starting to flow and I'm getting pretty excited about all that is new at IO.
Also new: I'm working on a brand new MacBook Air (11"). WOW. Setup took minutes (downloading upgrades hours). But with Google Chrome installed and my sync profile registered I had all my browser settings ready to go in a minute! Loving this!
Anyway, over the next 2 days I'll be documenting my sessions in this Blog... keeping notes. After the event I'll post some opinions over what I've heard.
Enjoy!
Mon Feb 21 15:20:00 CET 2011
Coding in Google Apps script can is fun (most of the time). In a recent project we've done some pretty cool stuff with the build in API's and using the oAuth Param class we've also ventured into other APIs available.
In a project currently underway, it turns out, GAppScript can sometimes be true pain in you know what too.
Recently an issue was detected with the xmlElement object in Google Apps Script. Fortunately there is a work around: JSON (or XMLShorthand). Writing your XML in a JSON Structure and presenting it to the SOAP service works great (for the SOAP-ENV:BODY. Not the SOAP Header). We've spend some time developing code to process the XML from a soap request into JSON (check out code blog). Code works great. Creates JSON as it should be... but here comes the pain: The XML we got from our initial request (a logon request) needs to go into the SOAP-ENV:HEADER but the API doesn't parse the JSON to XML as it does with the SOAP-ENV:BODY.
We've asked Google for a fix... but as you can imagine this is pretty painful. Specially because the project is due.
Check back for updates!
