OAuth2 was Re: google sheets - anybody doing anything besides mergGoogle

[Ben Rubinstein]

Ah, shame. It turned out it was (IIUC) just a change in the way Google did 
their tokens which exposed a bug, now fixed, in how LC did OAuth - nothing to 
do with the general API changing.

At any rate, I do have a very basic library which I use to read and write 
Google sheets, in case it's of use to anyone.

(I say library - currently it's a button I copy and paste to stacks where I 
need it, and "insert the script of". I've completely lost track of how real 
"libraries" should be packaged. Where should I look?)

Ben

On 21/07/2020 14:49, Mike Kerner wrote:
> I got impatient/spooked so we went another direction.  I think we're going to 
> use other tools.
> 
> On Thu, Jul 16, 2020 at 10:00 AM Ben Rubinstein via use-livecode 
> <use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>> wrote:
> 
>     Hi Mike,
> 
>     Brian Milby put me on to the solution for the OAuth problem:
>      > Check out bug 22557 / PR 7381.
>      > Line 247 of oath2.livecodescript need urlEncode removed
> 
>     Are you still interested in this, or are you covered now?
> 
>     regards,
> 
>     Ben
> 
>     On 11/03/2020 20:45, Ben Rubinstein via use-livecode wrote:
>      > Hi Mike,
>      >
>      > I haven't forgotten, but finally found time to take a look today and
>     started
>      > writing minimal comments, and thought I should at least test it - for some
>      > reason the authorisation isn't working. For whatever reason, the call to
>      > OAuth2 results in the error "Malformed auth code." So I can't get to
>     test what
>      > I'm sending.
>      >
>      > I'm unclear whether I've done something strange or wrong, or whether
>     Google
>      > has changed something that breaks LC's implementation. I've come across
>      > references which suggest that, but they date back to last year, and I
>     believe
>      > I've used this stack in January. (I also tried using LC 9.0.4 with the
>     same
>      > result.)
>      >
>      > I will try to get back to this. In the meantime, have you - or anyone -
>     found
>      > issues recently with OAuth2, in particular against any of the Google APIs?
>      >
>      > Ben
>      >
>      >
>      > On 08/03/2020 22:22, Mike Kerner via use-livecode wrote:
>      >> it might help us get started.  i'm going to probably put out an rfq to
>     wrap
>      >> the v4 rest api, because we're going to have to come to a solution, either
>      >> using lc or some other tool.
>      >>
>      >> On Sun, Mar 8, 2020 at 6:01 PM Ben Rubinstein via use-livecode <
>      >> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>>
>     wrote:
>      >>
>      >>> Mike,
>      >>>
>      >>> Very happy to share what I've got, but it's really not much - just a very
>      >>> thin
>      >>> wrapper round Google's API - and it's undocumented, mostly rough code -
>      >>> copied
>      >>> from one stack to the next, usually done in a tearing hurry!
>      >>>
>      >>> I'll try to pull something together, but please promise not to judge
>     me...
>      >>>
>      >>> Ben
>      >>>
>      >>> On 06/03/2020 15:13, Mike Kerner via use-livecode wrote:
>      >>>> Ben,
>      >>>> would you send me what you've got?  I was considering paying someone to
>      >>>> wrap the entire v4 api and dropping mergGoogle, so any head start would
>      >>> be
>      >>>> useful.  LC wants tribute to do the work (which is a little
>     disappointing
>      >>>> since we financed the original external, so we sort-of hoped that it
>      >>> would
>      >>>> become a thing, and it would get updated as required, but crap happens).
>      >>>>
>      >>>> On Thu, Mar 5, 2020 at 6:04 PM Ben Rubinstein via use-livecode <
>      >>>> use-livecode at lists.runrev.com
>     <mailto:use-livecode at lists.runrev.com>> wrote:
>      >>>>
>      >>>>> On 04/03/2020 20:37, Mike Kerner via use-livecode wrote:
>      >>>>>> is anyone using anything besides mergGoogle to work with google
>     sheets?
>      >>>>>> care to share, if you are?
>      >>>>>
>      >>>>> I'm just using the Google Sheets API directly from LiveCode - just
>      >>> pushing
>      >>>>> JSON back and forth. The API is limited, but what's there is very easy
>      >>> to
>      >>>>> work
>      >>>>> with - much better than manipulating xlsx files.
>      >>>>>
>      >>>>> I started using it to get data from clients, and then processing data
>      >>> and
>      >>>>> pushing it back into the sheets. I've also used on some experimental
>      >>> image
>      >>>>> processing, where I found that pushing the results of LiveCode
>     functions
>      >>>>> into
>      >>>>> a google sheet immediately gave me an nice interface in which to review
>      >>>>> the
>      >>>>> data, and then I could also use the spreadsheet functions to do
>      >>> evaluation
>      >>>>> and
>      >>>>> testing.
>      >>>>>
>      >>>>> Ben
>      >>>>>
>      >>>>> ____
>      >
>      > _______________________________________________
>      > use-livecode mailing list
>      > use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
>      > Please visit this url to subscribe, unsubscribe and manage your
>     subscription
>      > preferences:
>      > http://lists.runrev.com/mailman/listinfo/use-livecode
> 
>     _______________________________________________
>     use-livecode mailing list
>     use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
>     Please visit this url to subscribe, unsubscribe and manage your
>     subscription preferences:
>     http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> 
> -- 
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>     and did a little diving.
> And God said, "This is good."