From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Loury Subject: Re: Some thoughts on MobileOrg and its development .... Date: Mon, 18 Aug 2014 09:20:57 +0200 Message-ID: <87bnri9sbq.fsf@konixwork.incubateur.ens-lyon.fr> References: <87a97e1mp3.fsf@gmail.com> <87fvh6rte3.fsf@cern.ch> <8761hvs7ce.fsf@cern.ch> <87r40jqkx7.fsf@ericabrahamsen.net> <87bnrni467.fsf@yale.edu> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43308) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJHFZ-00051g-DC for emacs-orgmode@gnu.org; Mon, 18 Aug 2014 03:21:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XJHFV-0007jd-74 for emacs-orgmode@gnu.org; Mon, 18 Aug 2014 03:21:05 -0400 Received: from mail-wi0-x230.google.com ([2a00:1450:400c:c05::230]:35666) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJHFU-0007jJ-T5 for emacs-orgmode@gnu.org; Mon, 18 Aug 2014 03:21:01 -0400 Received: by mail-wi0-f176.google.com with SMTP id bs8so3219748wib.9 for ; Mon, 18 Aug 2014 00:20:59 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Xebar Saram , "Jorge A. Alfaro-Murillo" Cc: org mode --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Xebar Saram writes: > would LOVE to try it as well So would I ! >>> Henning Weiss writes: >>> >>>> I have been working over the last couple of months on a private >>>> prototype. I'm currently using it in my daily life and it works for me= . It >>>> uses Git (and only Git) for synchronization and doesn't use org-mobile= at >>>> all. The idea is that you keep all org files under git version control. >>>> Synchronization of all "clients" (apps or Emacs) is done against that >>>> repository. It is also possible to configure whether to use "ours" or >>>> "theirs" merge strategy when conflicts occur. I have focused on design= ing >>>> an app I can trust. >>>> It already has an outline view like MobileOrg, an agenda view, you can >>>> add and edit nodes, synchronize changes with a remote repository and >>>> synchronize scheduled entries to the calendar. I ported some of my code >>>> from MobileOrg, but a lot of it is written from scratch. I only used the android version, but I was not satisfied with its design either. I find the org double synchronization scheme (org <-> org mobile inbox <-> internal phone database) really annoying. Actually, I have been thinking about how to use my org file with my phone and the way I found the more practical was to synchronize the files with my phone using git (git annex actually) and using emacs in a debian chrooted environment. With the constantly evolving org-mode code in emacs-lisp, I don't think a re-implementation would survive. Besides, emacs-lisp allows to customize pretty everything, so much that two org-mode setup may easily be made barely compatible with each other. See the setup of Bernt Hansen for instance that is the most advanced I have seen so far=E2=81=B4. An other point of the evolving characteristic of org is the lack of definition of what the org-mode grammar is. Without this, it is most likely that someday, both emacs org-mode and mobile org will diverge at some point. There has been a very good draft of org mode syntax=C2=B9 made = by Nicolas Goaziou. May be this could be the basis of a new implementation, but it should be worked on to be considered stable and used as a reference for future implementations. Those are the reasons why I am not convinced that a new implementation would work and one of the main reasons each time I wanted to contribute to mobileorg-android, I was stopped by the feeling that it would be a useless effort (and the lack of time of course :-)). Therefore, I wonder if we could let emacs implementation do all the heavy stuff and customization, and only provide a mobile UI on top of it. Emacs could be accessed remotely or be run into the phone. In my Galaxy S3 with chrooted debian, emacs runs fast enough for my user experience not to be disturbed. I have tried the excellent org-ehtml=C2=B2 from Eric Schulte. It already allows to make basic edition of TODO entries and view the agenda views (only the basic org-agenda export to html for new). The main problem I see with this html/js view is that we often encounter strange issues due to bad browser implementations. I have been using the XML-RPC trac plugin=C2=B3 for a while now and I made = we wonder if we could reproduce this in the scope of mobile org. With an RPC interface, one would be free to create their own interface easily (at least python xml-rpc library is really easy to manipulate) and an official interface could emerge from that. The interface could provide functions like: =2D-8<---------------cut here---------------start------------->8--- getAgendaFiles() -> list of files names getTODOsFromFile(file) -> list of todos getAllTODOs() -> list of todos getAgendaViews() -> list of names getAgendaView(name) -> list of todos ? clockIn(id) clockOut(id) refile(id, parent_id) getKeywords() -> list of keywords setKeyword(id, keyword) ... =2D-8<---------------cut here---------------end--------------->8--- I don't know if those functions would be good, but they give an idea. =C2=B9 http://orgmode.org/worg/dev/org-syntax.html =C2=B2 https://github.com/eschulte/org-ehtml =C2=B3 http://trac-hacks.org/wiki/XmlRpcPlugin =E2=81=B4 http://doc.norang.ca/org-mode.html =2D- Konubinix GPG Key : 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJT8alZAAoJEHXSPO10ORBqlJYH+gOGpFfP3BhbJGrUi3fhWdjx kBI0HE6wYc9vvyIpnR5Ux2XF+qNpLsDAGrFEjD9yBCZMZq6yYrVX5rLbW5dh2PNf QUfYfz71IxrB03Z4x7pa+wXT/StwsDMAdGK7CAoD6SZKZI+QXQn2KjZA7JVexUUo IDQHCBKSSsVOKlHU2etrciUzT8WExkD7tW6lqyLYyuoFs6dqzuf+T81ht63ZVz/U jCzaQ2J8GiFD/FcuakoJT2F14CnpWQgEWtDs1eoWhu2GM9cYPbXBzhWeqmdHA+sM +9A+JxulYa6w9sJHOE4vMe16W6+PBI0RXwFIJR4aUxgVQWORvw4a+GJmcQSKs8g= =Uroa -----END PGP SIGNATURE----- --=-=-=--