From: Neil Jerram <neiljerram@gmail.com>
To: Diego Zamboni <diego@zzamboni.org>
Cc: Jude DaShiell <jdashiel@panix.com>,
Richard Lawrence <richard.lawrence@berkeley.edu>,
Org-mode <emacs-orgmode@gnu.org>
Subject: Re: mobile org
Date: Tue, 19 Nov 2019 09:16:18 +0000 [thread overview]
Message-ID: <CAKuG=vthnACzYpmVqRfgYiqPoKHo6gn=q_PazT0iFywtek8-vw@mail.gmail.com> (raw)
In-Reply-To: <CAGY83EfREp99T_UAN53LOx7vURvMStMoao_ZuU7f9U4ncmxq-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
If org-web and organice are browser-based, why do they need syncing? Could
the server be your regular non-mobile Org machine?
On Tue, 19 Nov 2019 at 08:57, Diego Zamboni <diego@zzamboni.org> wrote:
> Hm... organice is suspiciously similar to https://org-web.org/, which I
> had seen before. Even the Sample files are almost identical.
>
> Looking at the github history, organice seems to be a fork of org-web, but
> with more recent development.
>
> --Diego
>
>
> On Mon, Nov 18, 2019 at 10:10 PM Richard Lawrence <
> richard.lawrence@berkeley.edu> wrote:
>
>> Jude DaShiell <jdashiel@panix.com> writes:
>>
>> > Will mobile org work in Android PI? If not, any good alternatives
>> beyond
>> > orgsly available? I don't like to have to use dropbox and would like to
>> > plug a usb cord into my computer and synchtronize my orgmode files that
>> > way if possible.
>>
>> I saw this recently, and haven't seen it mentioned on the list:
>>
>> https://organice.200ok.ch/
>>
>> Here's an intro video: https://invidio.us/watch?v=aQKc0hcFXCk
>>
>> It's a browser-based interface rather than an app, so it should work
>> just about anywhere. It doesn't solve the syncing problem itself;
>> instead it allows you to sign in with Dropbox, Google Drive, or WebDAV.
>> Still not great if you're trying to avoid the proprietary services and
>> sync with a cable, but it looks like an interesting alternative to
>> Orgzly.
>>
>> --
>> Best,
>> Richard
>>
>>
[-- Attachment #2: Type: text/html, Size: 2437 bytes --]
next prev parent reply other threads:[~2019-11-19 9:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 0:01 mobile org Jude DaShiell
2019-11-18 0:13 ` Alex Roper
2019-11-18 2:03 ` Jude DaShiell
2019-11-18 2:14 ` Alex Roper
2019-11-18 2:34 ` Jude DaShiell
2019-11-18 17:04 ` Greg Troxel
2019-11-18 20:03 ` flow
2019-11-18 3:38 ` Charles Philip Chan
2019-11-18 12:42 ` Anssi Saari
2019-11-19 14:59 ` Charles Philip Chan
2019-11-18 21:08 ` Richard Lawrence
2019-11-19 8:56 ` Diego Zamboni
2019-11-19 9:16 ` Neil Jerram [this message]
2019-11-19 20:03 ` Richard Lawrence
2019-12-04 15:31 ` Jude DaShiell
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 12:49 Mobile org Paul Schlesinger
2017-01-25 23:13 ` Sean Escriva
2017-01-30 17:26 ` Kenneth Jacker
2017-01-30 17:59 ` Paul Schlesinger
2017-01-31 3:59 ` Sean Escriva
2010-04-24 13:11 mobile org charles snyder
2010-04-20 2:12 clsnyder
2010-04-20 7:44 ` Reinout van Rees
2009-09-02 15:44 Mobile org Marcelo de Moraes Serpa
2009-09-02 16:06 ` Matt Lundin
2009-09-02 18:31 ` Delwood Richardson
2009-10-03 6:25 ` [AvataR]
2009-12-10 21:11 ` Adam Spiers
2009-12-11 16:30 ` BKnoth
2009-09-02 20:53 ` Bernt Hansen
2009-09-03 6:33 ` Ian Barton
2009-09-07 18:54 ` Eric S Fraga, Eric S Fraga
2009-09-08 2:26 ` Miguel Fernando Cabrera
2010-02-03 14:57 ` news
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKuG=vthnACzYpmVqRfgYiqPoKHo6gn=q_PazT0iFywtek8-vw@mail.gmail.com' \
--to=neiljerram@gmail.com \
--cc=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
--cc=jdashiel@panix.com \
--cc=richard.lawrence@berkeley.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).