bug#5307: start of docs.google.com interface

bug#5307: start of docs.google.com interface

[Pace Willisson]

It would be neat to be able to access docs.google.com directly from
emacs, but there are many barriers.  I've taken a small step by
building out the core oauth stuff on top of
url-retrieve-synchronously:  I can do the authentication, get an xml
list of my documents, read the html contents of a file, and do a basic
translation of the file to an enriched text buffer.  I'm not going to
be able to work on it further for a good while, but perhaps someone is
interested in picking up from this point and taking the next steps.
Have a look at:

http://github.com/pacew/emacsg

(it's pretty messy now, but at least it demonstrates which key goes
where in the protocol)

Pace Willisson
pace@alum.mit.edu

Re: bug#5307: start of docs.google.com interface

[Ted Zlatanov]

On Sun, 3 Jan 2010 16:56:01 -0500 Pace Willisson <pace@alum.mit.edu> wrote: 

PW> It would be neat to be able to access docs.google.com directly from
PW> emacs, but there are many barriers.  I've taken a small step by
PW> building out the core oauth stuff on top of
PW> url-retrieve-synchronously:  I can do the authentication, get an xml
PW> list of my documents, read the html contents of a file, and do a basic
PW> translation of the file to an enriched text buffer.  I'm not going to
PW> be able to work on it further for a good while, but perhaps someone is
PW> interested in picking up from this point and taking the next steps.
PW> Have a look at:

PW> http://github.com/pacew/emacsg

PW> (it's pretty messy now, but at least it demonstrates which key goes
PW> where in the protocol)

Consider integrating it with Tramp, which will handle 90% of the
low-level file stuff.

Ted

bug#5307: start of docs.google.com interface

[Lars Ingebrigtsen]

Pace Willisson <pace@alum.mit.edu> writes:

> It would be neat to be able to access docs.google.com directly from
> emacs, but there are many barriers.  I've taken a small step by
> building out the core oauth stuff on top of
> url-retrieve-synchronously:  I can do the authentication, get an xml
> list of my documents, read the html contents of a file, and do a basic
> translation of the file to an enriched text buffer.  I'm not going to
> be able to work on it further for a good while, but perhaps someone is
> interested in picking up from this point and taking the next steps.
> Have a look at:
>
> http://github.com/pacew/emacsg
>
> (it's pretty messy now, but at least it demonstrates which key goes
> where in the protocol)

(I'm going through old bug reports that unfortunately didn't get any
response at the time.)

This seems like a good idea for a (M)ELPA package, but it's probably
outside the scope of the Emacs bug tracker to proceed with.  So I'm
closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#5307: start of docs.google.com interface

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > It would be neat to be able to access docs.google.com directly from
  > > emacs, but there are many barriers.

It would be good _provided_ it doesn't involve running nonfree software
(in particular, Javascript code from Google itself).

Access to Google Docs which bypasses that Javascript code would
be a great step forward, worth celebrating.

-- 
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)