emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: Matthew Jones <bsdmatburt@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Agenda in MobileOrg for Android
Date: Tue, 9 Apr 2013 22:27:55 +0200	[thread overview]
Message-ID: <20130409222755.064b6dd5@aga-netbook> (raw)
In-Reply-To: <CABSYn2irEu0e6B5E5FJqH_Lgdfqdo4xJ8m9noCSnu3C2LvUSdw@mail.gmail.com>

Dnia 2013-04-09, o godz. 14:24:24
Matthew Jones <bsdmatburt@gmail.com> napisał(a):

> 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:

Hi, thanks for this answer!

> - 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.

I see.  OTOH, one argument *against* a database (as opposed to parsing
text files) might be exactly preserving the formatting etc. of files (of
course, with all the syncing stuff this is not important anyway).

> - 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.

That's interesting.  I would be very glad to learn what might the
pitfalls of "just overwriting files" be; it may be the case that "just
overwriting" would work well with *my personal* use pattern of
Org-mode, and that would be why I don't understand MobileOrg's approach.

And I guess that the decision was in fact made by the devs of MobileOrg
for iOS (which I guess predates the Android app).

> - 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.

I know, I know, I'm sorry.


* Yes, I did uninstall, but I've reinstalled MobileOrg again after
  reading this thread.  I'll try to set it up again.  I installed from
  the Google Play; is it better to use the github repo?  It says
  "0.9.7" in the release notes on the wiki, Google Play says it's
  0.9.8, and maybe it would be better to use master or even 0.9.10
  (looking at the branches on github)?  Where do I find the info about
  installing the bleeding edge version from github on my phone (I'm
  quite new to Android, as I mentioned.)

* I did not leave a one-star review; I guess I'm too lazy for that, but
  also it would be a bit unfair without further investigation of my

* I am very busy these days, but I'll try hard to start using MobileOrg
  and (if the problems I had persist), I'll try to report them on
  MobileOrg's mailing list.  In fact, my problems were twofold:
  firstly, syncing didn't "Just Work™" (sometimes I got errors on
  MobileOrg, sometimes in Emacs), and some of the UI choices *did*
  suck.  As soon as I find some time, I'll try to describe exactly what
  I mean by this, so that either it could get improved or I could get
  convinced that it's my usage that sucks (which is obviously possible,
  especially given my lack of experience).


Marcin Borkowski
Adam Mickiewicz University

  reply	other threads:[~2013-04-09 20:28 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
2013-04-09 20:27           ` Marcin Borkowski [this message]
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:

  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=20130409222755.064b6dd5@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --cc=bsdmatburt@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).