emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins < jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Agenda in MobileOrg for Android
Date: Mon, 8 Apr 2013 01:20:34 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130408T030008-276@post.gmane.org> (raw)
In-Reply-To: 20130407151332.218212de@aga-netbook

Marcin Borkowski <mbork <at> wmi.amu.edu.pl> writes:

> > 2. When I choose the menu and then "Outline", I can see the outline.
> > But when I choose menu and then "Agenda", I see nothing but the
> > title ("Agenda") and a "plus" button in the upper right corner.
> >
> > (a) Shouldn't there be an agenda on the screen?

No, not yet. This is a new feature, in which you define agenda views in 
MobileOrg, and MobileOrg will refresh those agendas dynamically based on its 
own database. You'll see your MobileOrg edits immediately, without syncing 
back to emacs. (This also means John's guess about choosing agenda views to 
push from emacs is not correct. "Pushed" agendas appear under the Agendas 
heading in the outline. Dynamic agendas are separate.)

If you don't define dynamic agendas within MobileOrg, then the list of 
available dynamic agendas would be empty. What's missing is explanatory text 
onscreen.

This feature indeed has some serious bugs in the currently released version 
(beta, btw -- pre-1.0) but I just saw a notice on the MobileOrg Android 
mailing list that a fix was just checked into the source repository.

> the key seems to be "too hard to use efficiently"...  I am afraid that
MobileOrg for Android) is indeed much more difficult to use than the
Emacs version.  The strength of Org is that it is easy to use (and
efficient in terms of keystrokes etc.).

It might be appropriate to discuss specific use cases that could be improved, 
instead of just stating "it's not efficient." (That's more polite, but it 
conveys about the same amount of useful information as "it sucks" -- i.e., 
none at all).

You did mention syncing. MobileOrg uses a database internally. Maybe that's 
easier to manage in java? I'm only speculating, don't know the reason for 
sure. It's a reasonable guess that parsing org files in java could be more 
difficult than in ELisp. Anyway, I haven't found the syncing requirement to be 
especially onerous. At least, the benefits of MobileOrg are significant enough 
for me that syncing does not negate them.

E.g., my department sent a sms to my phone explaining upcoming holiday 
schedules. I copied the text into a new node (while away from the computer) 
and later, synced. When some students asked what was up with the schedule, it 
was just a couple of taps on my phone to navigate the headings and read it.

The point being, MobileOrg is actually quite useful for capturing notes, 
adding calendar events etc on-the-go, and integrating that into the emacs org 
files.

hjh

  parent reply	other threads:[~2013-04-08  7:06 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 [this message]
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
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=loom.20130408T030008-276@post.gmane.org \
    --to=jamshark70@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).