From: Sean Escriva <sean.escriva@gmail.com>
To: Jacek Generowicz <jacek.generowicz@cern.ch>,
emacs-orgmode <emacs-orgmode@gnu.org>
Cc: Alexis <flexibeast@gmail.com>
Subject: Re: Some thoughts on MobileOrg and its development ....
Date: Wed, 13 Aug 2014 21:47:03 -0400 [thread overview]
Message-ID: <m2vbpvzvu0.fsf@webframp.com> (raw)
In-Reply-To: <87fvh6rte3.fsf@cern.ch>
Greetings Org users!
(Current MobileOrg iOS maintainer here)
Great to read some feedback. It's often hard to know who really cares if
MobileOrg even exists.
Jacek Generowicz <jacek.generowicz@cern.ch> writes:
> Alexis <flexibeast@gmail.com> writes:
>
>> i can't help but wonder if the 'MobileOrg' endeavour needs a reboot.
>
> It seems clear that it does.
>
>> More specifically, it seems to me that rebuilding MobileOrg as a single
>> project [...] might be a way forward,
>
> This is vital!
I haven't talked with Matburt for some time now, so I don't want to
speak for him.
However from my perspective there's a huge value in having a single
codebase. Basically my preference is to do whatever will allow the most
contributors to help out.
>
>> on top of Apache Cordova:
>>
>> https://cordova.apache.org/
>
> I'd just like to float Kivy as another possibility:
>
> http://kivy.org
>
> What makes Kivy interesting to me in this context (apart from its
> cross-platform nature) is its excellent support of gestures, which gives
> me (the perhaps naive) hope that a little more than an utterly trivial
> feature set might be provided on the mobile form factor.
If Cordova or Kivy are a way to that I'm open to looking at them, but
don't have experience with either.
I am comfortable with python so Kivy appeals to me personally.
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.
There's tons of options for possible paths here (even
https://wukix.com/mocl for fellow LISPers) but the key in my mind is to
support a community of contributors.
>
>> 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.
As of the iOS version specifically, I have held off updating due to a
few requests to maintain support for older devices.
My preference in the short term for iOS would be to update the code to
the latest sdk and add a few minor features if needed, but then
determine the best way forward to maintain a single common functional
base.
I am an owner on the github org: https://github.com/MobileOrg and it
would be excellent to make it the central org for any efforts. I'm happy
to help that happen however I can.
--
-sean
next prev parent reply other threads:[~2014-08-14 1:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 0:56 Some thoughts on MobileOrg and its development Alexis
2014-08-09 4:13 ` Xebar Saram
2014-08-09 4:22 ` David Masterson
2014-08-13 1:07 ` Ashton Kemerling
2014-08-13 1:47 ` David Wagle
2014-08-13 2:23 ` Ashton Kemerling
2014-08-13 2:45 ` Alexis
2014-08-13 4:04 ` Ashton Kemerling
2014-08-13 8:10 ` Jacek Generowicz
2014-08-13 22:23 ` Carlos Sosa
2014-08-14 0:54 ` Alexis
2014-08-13 2:59 ` Alexis
2014-08-09 7:53 ` Jacek Generowicz
2014-08-14 1:47 ` Sean Escriva [this message]
2014-08-14 2:10 ` Ashton Kemerling
2014-08-14 10:17 ` Jacek Generowicz
2014-08-14 12:17 ` Henning Weiss
2014-08-14 13:07 ` Eric Abrahamsen
2014-08-14 13:36 ` Jorge A. Alfaro-Murillo
2014-08-14 15:29 ` Xebar Saram
2014-08-18 7:20 ` Samuel Loury
2014-09-10 19:39 ` Samuel Loury
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=m2vbpvzvu0.fsf@webframp.com \
--to=sean.escriva@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=flexibeast@gmail.com \
--cc=jacek.generowicz@cern.ch \
/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).