Ben,
I’d find a sample stack to be useful. I’ll leave details of what constitutes a
“library” to others. There are some best practices, tho. What I see is usually
a text stack with that main handlers with a sample stack that demos basic calls.
That said, if you don’t have the time to get into
Hi Bill (and Neville)
Happy to post it - I'll try to do a bit of cleanup and commenting first.
(Honestly I think it's probably just going to be an email to the list.) Afore
I do, I had this question:
(I say library - currently it's a button I copy and paste to stacks where I
need it, and
Ben,
Any chance of posting a demo stack somewhere? It sounds very useful.
Thanks,
Bill
William Prothero
http://es.earthednet.org
> On Jul 22, 2020, at 10:13 AM, Ben Rubinstein via use-livecode
> wrote:
>
> Ah, shame. It turned out it was (IIUC) just a change in the way Google did
> their
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
I once did that, to read out the values on a sheet. But I can't remember if
I used OAuth2 for that.
Op di 21 jul. 2020 15:51 schreef Mike Kerner via use-livecode <
use-livecode@lists.runrev.com>:
> I got impatient/spooked so we went another direction. I think we're going
> to use other tools.
>
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@lists.runrev.com> wrote:
> Hi Mike,
>
> Brian Milby put me on to the solution for the OAuth problem:
> > Check out bug
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:
@Matthias: "i found a forum post from mimu which included also a
GoogleCalendarTest stack. http://forums.livecode.com/viewtopic.php?t=31840;
Yes, correct. Thanks for the hint! This is the one I am using. The scripts
are very good and allow to expand the idea of connecting to Google
Services. It
Roland,
i found a forum post from mimu which included also a GoogleCalendarTest stack.
http://forums.livecode.com/viewtopic.php?t=31840
Is that the one you are referring to?
Matthias
> Am 13.03.2020 um 14:00 schrieb R.H. via use-livecode
> :
>
> If this would help...
>
> I am using
If this would help...
I am using OAuth2 with the Google Calendar with a stack that was originally
developed by Denver77 and had been posted the stack "GoogleCalendarTest" to
the Forum in 2018. It explains clearly how to use Google's oAuthClient and
actually, I was able to receive the client id,
2:47 PM
> To: use-livecode@lists.runrev.com
> Cc: Richard Gaskin
> Subject: Re: OAuth2 was Re: google sheets - anybody doing anything besides
> mergGoogle
>
> J. Landman Gay wrote:
> > I wonder if the crashes are a problem with a different OS (I'm > on
> Mac,) or some
Re: OAuth2 was Re: google sheets - anybody doing anything besides
mergGoogle
J. Landman Gay wrote:
> I wonder if the crashes are a problem with a different OS (I'm > on
Mac,) or something about your stack. I haven't had any debugging > crashes
since the fix was implemented.
...
J. Landman Gay wrote:
> I wonder if the crashes are a problem with a different OS (I'm
> on Mac,) or something about your stack. I haven't had any debugging
> crashes since the fix was implemented.
...
> I know typing can be very slow on Windows but it
> isn't bad on Mac.
I had an confounding
I also see the red dot misalignment (still using 9.5.1 rc 1). Since I use LC
virtually every day to make changes and fixes to the app we use, I cannot
really participate in DP's.
Bob S
> On Mar 12, 2020, at 11:17 , J. Landman Gay via use-livecode
> wrote:
>
> On 3/11/20 9:50 PM, Sean Cole
On 3/11/20 9:50 PM, Sean Cole (Pi) via use-livecode wrote:
9.5.1 and 9.6 dp2 are still exhibiting breakpoint crashes. Not
as often as before but, still, there are occurrences. And for some very odd
reason an early sign it's going to become a problem I notice the line
numbers don't scroll with
monte has previously said that merggoogle is using a c-library.
the "need" for merggoogle is to not rewrite the existing code and/or write
a new library from scratch. otherwise i wouldn't need to issue an rfq to
have someone write a library. i could have it done for free.
or i would be overrun
Sean Cole wrote:
> On Thu, 12 Mar 2020 at 00:17, Richard Gaskin via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
>> I had thought the problem at that time was that your app was using
>> Google's older auth method, before they switched to OAth2.
>
> Correct. But not the oAuth Lib
Mike Kerner wrote:
> 6. there doesn't seem to be any interest in updating merggoogle.
It'll be good to hear from Monte on this, but I'd guess the reason
merGoogle isn't actively supported is because the meat of it is handling
authentication, and the REST API itself if pretty straightforward.
see the rfq i posted. there are a variety of issues in merggoogle
1. mac/ios only
2. doesn't seem to work in newer versions of lc for some reason (works in
9.0.1, for instance, but not in 9.5.x)
3. google is going to shut off...something...that merggoogle is using in
september. i don't know what
On Thu, 12 Mar 2020 at 00:17, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I had thought the problem at that time was that your app was using
> Google's older auth method, before they switched to OAth2.
>
Correct. But not the oAuth Lib directly anyway. What bothered
The crasher was fixed. I think Sean is talking about how scrolling doesn't
change the position of the red dots. That seems minor, since it fixes
itself once any keyboard activity happens. Annoying maybe, but not
critical. The bad bugs usually get fixed.
Panos said the team is aware of the new
I had thought the problem at that time was that your app was using
Google's older auth method, before they switched to OAth2.
The Oath2 lib is in LC's Github repository:
https://github.com/livecode/livecode/blob/develop/extensions/script-libraries/oauth2/oauth2.livecodescript
So now I'm
Faith, I am told, is the 'Assured expectation of things not yet beheld'.
There is very little in the way of evidence or assurance to inspire faith.
Unless it's there and I'm looking in the wrong places. As I say, script
editor is still messed up and thats where ALL of our work gets done. I'm
tired
On 3/11/20 5:06 PM, Pi Digital via use-livecode wrote:
I’m guessing uptake for LC4FM is as low as I had predicted it would be,
especially based on the forum discussions.
Forum participation is not a good indication of uptake, and I wouldn't venture a guess based on
that. I don't think folks
I had a major issue with oAuth when google first switched off the old
credentials format which caused me to have a major breakdown and lost all of my
clients as a result. Merg had not been updated to reflect and prepare the the
change so caused it to catastrophically breakdown on the very day
25 matches
Mail list logo
