From: "Richard Moreland" <rlm@ncogni.to>
To: Tommy Kelly <tommy.kelly@verilab.com>,
Org-mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Re: MobileOrg on DropBox for Teams
Date: Sun, 28 Nov 2010 09:41:01 -0500 [thread overview]
Message-ID: <1290955261.27101.1407521573@webmail.messagingengine.com> (raw)
In-Reply-To: <m2fwum9h30.fsf@verilab.com>
On Sat, 27 Nov 2010 23:01 -0600, "Tommy Kelly" <tommy.kelly@verilab.com>
wrote:
> > You should be able to rename the MobileOrg directory from within the
> > web interface once you've linked MobileOrg to your Dropbox account.
>
> Thanks Richard, that worked fine.
>
> But does that mean there's a bit of coordination to manage if multiple
> users all decided they want to use MobileOrg? In turn, each user would
> get their top level MobileOrg folder up and running, then move it down
> a level, so as to make space for the next user who'd do the same?
I'm not sure how your account sharing is setup: if you are all using
the same credentials, you will probably run into trouble. Each Dropbox
account will only get a single 'magic' MobileOrg folder, so if everyone
is sharing a single login, I don't see how it will work. It would
probably be possible to change MobileOrg to support specifying the
folder in your Dropbox account that it should use, but I have
reservations about that. The way I use the API now, MobileOrg only has
access to its own sandbox/special folder. There's no way it could
accidentally mess with/expose/etc your other Dropbox files.
The other option is to let each user have their own Dropbox account and
simply share folders from a master account to each person.
Hope this helps,
Richard
next prev parent reply other threads:[~2010-11-28 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 19:18 MobileOrg on DropBox for Teams Tommy Kelly
2010-11-27 19:31 ` Richard Moreland
2010-11-28 5:01 ` Tommy Kelly
2010-11-28 14:41 ` Richard Moreland [this message]
2010-11-28 15:54 ` Tommy Kelly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1290955261.27101.1407521573@webmail.messagingengine.com \
--to=rlm@ncogni.to \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.