From: Jacek Generowicz <jacek.generowicz@cern.ch>
To: Sean Escriva <sean.escriva@gmail.com>
Cc: Alexis <flexibeast@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Some thoughts on MobileOrg and its development ....
Date: Thu, 14 Aug 2014 12:17:53 +0200 [thread overview]
Message-ID: <8761hvs7ce.fsf@cern.ch> (raw)
In-Reply-To: <m2vbpvzvu0.fsf@webframp.com>
Sean Escriva <sean.escriva@gmail.com> 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.
next prev parent reply other threads:[~2014-08-14 10:19 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
2014-08-14 2:10 ` Ashton Kemerling
2014-08-14 10:17 ` Jacek Generowicz [this message]
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=8761hvs7ce.fsf@cern.ch \
--to=jacek.generowicz@cern.ch \
--cc=emacs-orgmode@gnu.org \
--cc=flexibeast@gmail.com \
--cc=sean.escriva@gmail.com \
/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).