From: Matthew Jones <bsdmatburt@gmail.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Agenda in MobileOrg for Android
Date: Tue, 9 Apr 2013 14:24:24 -0400 [thread overview]
Message-ID: <CABSYn2irEu0e6B5E5FJqH_Lgdfqdo4xJ8m9noCSnu3C2LvUSdw@mail.gmail.com> (raw)
In-Reply-To: <20130408112847.769a44d3@aga-netbook>
[-- Attachment #1: Type: text/plain, Size: 3854 bytes --]
Hey guys, I'm one of the maintainers of MobileOrg for Android. We've
worked really hard to try to implement as many of the features of org-mode
as we can and make it comfortable to use for the majority of people. A
couple of points:
- Originally we were just storing the org files and parsing those on demand
instead of using a database. This proved extremely cumbersome when we
wanted to add more features, and it really did not scale well when people
had very large org files. We made a decision a while ago to switch to a
database almost exclusively for this reason, but there were a lot of other
smaller reasons that also made it worthwhile.
- The reason we do syncing the way that we do is to fit into org-mode's
org-mobile-* concept. Keeping multiple sets of plain text files in sync
with emacs in the loop is no simple task. The org-mobile-* functions were
already defined and well used when I started writing the Android port of
MobileOrg. It may be suboptimal but currently it is the best and easiest
(from the development side) way to keep a remote device and an instance of
emacs in sync. I'm actually not even sure if the org-mobile-* routines are
even maintained anymore. The synchronization problem is not as easy as
just overwriting the files, however.
- If you have issues and you don't tell us then we have no way of helping
you and the problem might not go away. We try to stay on top of
showstopping issues for our users (we have an email address and a bug
tracker linked to in the app store) unfortunately some folks just leave a 1
star review and uninstall and never contact us.
On Mon, Apr 8, 2013 at 5:28 AM, Marcin Borkowski <mbork@wmi.amu.edu.pl>wrote:
> Dnia 2013-04-08, o godz. 06:52:02
> James Harkins <jamshark70@gmail.com> napisał(a):
>
> > As it happens, one of the lead developers of mobileorg started a
> > thread on the MobileOrg-Android mailing list asking for issues that
> > need to be addressed, and features that are needed, before it's ready
> > for 1.0.
>
> Well, I didn't know about the existence if that list;).
>
> > I'm using MobileOrg and enjoying it in general. I find it terribly
> > useful and not especially cumbersome. The initial setup was a bit of a
> > trek for me, because I don't have access to dropbox where I live
> > (mainland China). Ultimately, because of unreliable connections to
> > Ubuntu One, I ended up running my own WebDAV server locally and
> > syncing at home over the WLAN.
> >
> > Otherwise, the only thing I had to adapt in my org/emacs usage was to
> > schedule appointments (C-c C-s) instead of using timestamps for them
> > (C-c .). I'm actually not crazy about that -- I'd rather use
> > timestamps -- but it does work. (Come to think of it, I should propose
> > that as one of the 1.0 issues... or check if it's changed since the
> > last time I tried.) Items with scheduled or deadline timestamps appear
> > in the Android calendar, and there is a preference in MobileOrg to
> > attach reminders automatically. (One remaining point here -- another
> > 1.0 issue -- is that creating a new node in MobileOrg with a schedule
> > or deadline doesn't show up in the phone calendar until after
> > syncing. I'll bring that up on the M/O mailing list.)
> >
> > I find that creating new nodes and minor editing of existing ones is
> > not at all inconvenient. I don't see a big issue for the workflows
> > that Marcin subsequently identified as being critical for this kind of
> > app. They're already there.
> >
> > hjh
>
> As I wrote in my other email, I'll give it a try - but I'm very much
> tempted to try to write my own implementation, for the sake of learning.
>
> Best,
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Adam Mickiewicz University
>
>
[-- Attachment #2: Type: text/html, Size: 4719 bytes --]
next prev parent reply other threads:[~2013-04-09 18:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 1:52 Agenda in MobileOrg for Android Marcin Borkowski
2013-03-24 2:04 ` John Hendy
2013-04-07 13:13 ` Marcin Borkowski
2013-04-07 21:16 ` David Rogers
2013-04-07 21:41 ` Marcin Borkowski
2013-04-08 4:33 ` David Rogers
2013-04-08 6:24 ` Marcin Borkowski
2013-04-08 1:20 ` James Harkins
2013-04-08 9:26 ` Marcin Borkowski
2013-04-09 10:19 ` Gareth Smith
2013-04-08 6:52 ` James Harkins
2013-04-08 9:28 ` Marcin Borkowski
2013-04-09 18:24 ` Matthew Jones [this message]
2013-04-09 20:27 ` Marcin Borkowski
2013-04-09 20:51 ` Matthew Jones
2013-04-09 21:36 ` Marcin Borkowski
2013-04-09 22:06 ` John Hendy
2013-04-23 10:50 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE (was: Agenda in MobileOrg for Android) Karl Voit
2013-04-24 4:41 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE Rémi Vanicat
2013-04-24 7:38 ` Eric S Fraga
2013-04-24 14:46 ` Rémi Vanicat
2013-04-24 17:21 ` Henning Weiss
2013-04-24 17:33 ` MobileOrg and repeating events (was: Android MobileOrg: appointments without SCHEDULED/DEADLINE) Karl Voit
2013-04-24 17:15 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE (was: Agenda in MobileOrg for Android) Henning Weiss
2013-04-24 17:30 ` Karl Voit
2013-04-25 8:55 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE Eric S Fraga
2013-04-15 12:45 ` Agenda in MobileOrg for Android Andreas Leha
2013-04-15 15:24 ` Bastien
2013-04-15 18:36 ` Andreas Leha
2013-05-12 1:55 ` mobileorg-android
2013-05-13 3:00 ` [mobileorg-android] " James Harkins
2013-05-13 13:28 ` Marcin Borkowski
-- strict thread matches above, loose matches on Subject: below --
2013-04-07 17:54 Itai kloog
2013-04-09 18:09 Jorge A. Alfaro Murillo
2013-04-09 18:18 ` David Rogers
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=CABSYn2irEu0e6B5E5FJqH_Lgdfqdo4xJ8m9noCSnu3C2LvUSdw@mail.gmail.com \
--to=bsdmatburt@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).