I've been using ClientLogin authentication (service: 'writely') to
obtain the document list feed via the Google Doc List APIs.  I'm quite
interested in grabbing a simple HTML (e.g., no editing)
representations of the documents.

The <content src="<url>"> element seems to be the way to do this, and
for 'document' types (writely), life is good:  an authenticated GET
against the content src url returns nice, clean, simple, script-free
HTML which is easy to render.

However, the same access method for spreadsheets and presentation
doesn't yield the same results.

Specifically, for spreadsheets, the returned content src url is of the
form:

http://spreadsheets.google.com/fm?fmcmd=102&key={foo}

After doing my authenticated GET, I receive an HTTP 200, but no data.
Hmm, ok, authentication issue maybe?  I can paste the given URL into a
browser, and poof, the (über simple script-free) HTML version of
spreadsheet is (mockingly) staring back at me.

Question 1[a,b]: Should I be able to get back what I'm after here
(simple script free HTML)?  Am I authenticated incorrectly here?
--

For presentations, the returned SRC url is of the (more familiar, same
as the 'document' type) form:
http://docs.google.com/RawDocContents?action=fetch&docID={foo}

This time, life is better, I do get back contents, but it appears to
be a "editing" version replete with all the javascript glory and a
tidy little "browser not supported" notice.

So that leads me to my 2nd question:  Is there a version of
presentations available via the API that is a simple HTML view-only
version that is suitable for any browser?

Thanks!
-Steve
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to