On Wed, Oct 11, 2017 at 1:02 PM Ben Rubinstein via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> In principle I think that a new app, e.g. built in LiveCode, could
> perfectly
> happy operate on a number of accounts simultaneously. But my proposal in no
> way prevents that - the code
Most of the filestore apps, be they box, dropbox, google drive,
oneDrive, etc. only operate on one account at a time. That's one of the
nice things about the API's - you can operate on an unlimited number from
your app.
On Wed, Oct 11, 2017 at 2:00 PM, Ben Rubinstein via use-livecode <
> Does Dropbox limit syncing to a single account?
As far as I know, yes.
That doesn't mean the API enforces this - only that every app and interface
I've come across for it does - you log in as a given account, and you're
operating on that account. There is a folder "~/Dropbox" (or Windows
That's why I raise it for discussion here first.
My guess is that if this is only in LC 9, and only since DP-7, then the number
of people already using it will be small - certainly in proportion to the
number who will go on to use it in years ahead!
And for those small number of people
Ben Rubinstein wrote:
The new Dropbox library is (going to be) great. But while it's still only in
DP, can I suggest a modest improvement?
Every single command in the library takes an access token as the first
parameter. Given that most uses of the library will involve multiple calls;
and
And I don't know how modest it will be - the syntax of every command in the
library would have to be updated, which means everyone's code (who is using
the library) would have to update it.
We could also have a new dropbox library that implements this, but then it
would be up to the team to
so file a qr. since it's written in LC it should be doable by either of
us...or anyone
On Wed, Oct 11, 2017 at 12:12 PM, Ben Rubinstein via use-livecode <
use-livecode@lists.runrev.com> wrote:
> The new Dropbox library is (going to be) great. But while it's still only
> in DP, can I suggest a
The new Dropbox library is (going to be) great. But while it's still only in
DP, can I suggest a modest improvement?
Every single command in the library takes an access token as the first
parameter. Given that most uses of the library will involve multiple calls;
and the cases where an app is
