From mboxrd@z Thu Jan 1 00:00:00 1970 From: Henning Weiss Subject: Re: Some thoughts on MobileOrg and its development .... Date: Thu, 14 Aug 2014 14:17:50 +0200 Message-ID: References: <87a97e1mp3.fsf@gmail.com> <87fvh6rte3.fsf@cern.ch> <8761hvs7ce.fsf@cern.ch> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c32efaaf6bd7050095e434 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39731) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XHtyb-0005yB-6h for emacs-orgmode@gnu.org; Thu, 14 Aug 2014 08:17:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XHtyZ-0002fs-En for emacs-orgmode@gnu.org; Thu, 14 Aug 2014 08:17:53 -0400 Received: from mail-ob0-x234.google.com ([2607:f8b0:4003:c01::234]:63242) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XHtyZ-0002eI-6i for emacs-orgmode@gnu.org; Thu, 14 Aug 2014 08:17:51 -0400 Received: by mail-ob0-f180.google.com with SMTP id uy5so858486obc.25 for ; Thu, 14 Aug 2014 05:17:50 -0700 (PDT) In-Reply-To: <8761hvs7ce.fsf@cern.ch> 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: Jacek Generowicz Cc: emacs-orgmode , Alexis , Sean Escriva --001a11c32efaaf6bd7050095e434 Content-Type: text/plain; charset=UTF-8 Hi, My name is Henning and I am the co-maintainer of MobileOrg Android. The reason I stopped working on the project is partially the lack of time, but also because I didn't believe in the design of org-mobile-push/pull and edit nodes. Almost half of the bugs on our issue tracker are with regards to synchronization. Our mailing list is also full with questions about how to set synchronization up. This is the reason I tried to come up with a better design based on git synchronization. And I did ;) 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 designing 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 don't feel comfortable publishing it for general consumption yet. There are still some rough edges for the end user, but the core functionality is done and it works reliably. If you want to help development and testing, feel free to contact me :) Henning On Thu, Aug 14, 2014 at 12:17 PM, Jacek Generowicz wrote: > > Sean Escriva writes: > > >>> https://cordova.apache.org/ > > >> http://kivy.org > > > From the little experience I have with them, cross platform frameworks > > do suffer from a loss of fidelity compared to native applications but > > as mentioned that may be an acceptable trade off. > > We are talking about interfacing to org-mode, an Emacs mode: I don't > think that the target audience is one which excessively values > platform-specific look-and-feel and has an insurmountable aversion to > idiosyncratic interfaces :-) > > > There's tons of options for possible paths here > > Do you have a decent resource for seeking them out? I found good ones > surprisingly difficult to find. > > > (even https://wukix.com/mocl for fellow LISPers) but the key in my > > mind is to support a community of contributors. > > Yes, I almost mentioned Mocl along with Kivy, but two things stopped me: > > + Mocl is not free, which will not help increase the number of > contributors, > > + I get the feeling that the average org-mode user is even less Lispy > than your average Emacs user, Elisp notwithstanding. > > >>> Unfortunately, due to other existing commitments, i wouldn't be able > >>> to take point on such a reboot. > >> > >> The dreamer in me thinks this might be the itch-to-scratch that finally > >> motivates me to getting to grips with Kivy; the realist in me is pretty > >> certain that I fall into the same category as you. > > > > Realistically this is the issue in most cases, plenty of well meaning > > help but not a lot of time to do anything. Life gets in the way. > > For me, after life getting in the way, by far the biggest barrier to > contribution is the platform-specificity of the projects: I simply can't > be bothered to even think about contributing to something which only be > useful to "half" the potential users. > > --001a11c32efaaf6bd7050095e434 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

My name is Henning and I am the co-= maintainer of MobileOrg Android.

The reason I stop= ped working on the project is partially the lack of time, but also because = I didn't believe in the design of org-mobile-push/pull and edit nodes. = Almost half of the bugs on our issue tracker are with regards to synchroniz= ation. Our mailing list is also full with questions about how to set synchr= onization up. This is the reason I tried to come up with a better design ba= sed on git synchronization. And I did ;)

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 work= s for me. It uses Git (and only Git) for synchronization and doesn't us= e org-mobile at all. The idea is that you keep all org files under git vers= ion control. Synchronization of all "clients" (apps or Emacs) is = done against that repository. It is also possible to configure whether to u= se "ours" or "theirs" merge strategy when conflicts occ= ur. I have focused on designing an app I can trust.

It already has an outline view like MobileOrg, an agend= a view, you can add and edit nodes, synchronize changes with a remote repos= itory and synchronize scheduled entries to the calendar. I ported some of m= y code from MobileOrg, but a lot of it is written from scratch.

I don't feel comfortable publishing it for general = consumption yet. There are still some rough edges for the end user, but the= core functionality is done and it works reliably. If you want to help deve= lopment and testing, feel free to contact me :)

Henning


<= div class=3D"gmail_quote">On Thu, Aug 14, 2014 at 12:17 PM, Jacek Generowic= z <jacek.generowicz@cern.ch> wrote:

Sean Escriva <sean.escriva@gma= il.com> writes:

>>> http= s://cordova.apache.org/

>> =C2=A0 =C2=A0http://= kivy.org

> From the little experience I have with them, cross platform frameworks=
> do suffer from a loss of fidelity compared to native applications but<= br> > as mentioned that may be an acceptable trade off.

We are talking about interfacing to org-mode, an Emacs mode: I don= 9;t
think that the target audience is one which excessively values
platform-specific look-and-feel and has an insurmountable aversion to
idiosyncratic interfaces :-)

> There's tons of options for possible paths here

Do you have a decent resource for seeking them out? I found good ones=
surprisingly difficult to find.

> (even https://wuk= ix.com/mocl for fellow LISPers) but the key in my
> mind is to support a community of contributors.

Yes, I almost mentioned Mocl along with Kivy, but two things stopped = me:

=C2=A0 + Mocl is not free, which will not help increase the number of
=C2=A0 =C2=A0 contributors,

=C2=A0 + I get the feeling that the average org-mode user is even less Lisp= y
=C2=A0 =C2=A0 than your average Emacs user, Elisp notwithstanding.

>>> Unfortunately, due to other existing commitments, i wouldn'= ;t be able
>>> to take point on such a reboot.
>>
>> The dreamer in me thinks this might be the itch-to-scratch that fi= nally
>> motivates me to getting to grips with Kivy; the realist in me is p= retty
>> certain that I fall into the same category as you.
>
> Realistically this is the issue in most cases, plenty of well meaning<= br> > help but not a lot of time to do anything. Life gets in the way.

For me, after life getting in the way, by far the biggest barrier to<= br> contribution is the platform-specificity of the projects: I simply can'= t
be bothered to even think about contributing to something which only be
useful to "half" the potential users.


--001a11c32efaaf6bd7050095e434--