emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Neil Jerram <neiljerram@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: Org Mode List <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Best practice for providing an Org-based application?
Date: Tue, 10 Sep 2019 22:49:01 +0100	[thread overview]
Message-ID: <CAKuG=vvG7t4EcT4+mch_behRR49dqMxQW-WF0HWxm4pC4Koneg@mail.gmail.com> (raw)
In-Reply-To: <20190910134453.GT3590@protected.rcdrun.com>

[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]

Thanks Jean for your reply...

On Tue, 10 Sep 2019 at 14:53, Jean Louis <bugs@gnu.support> wrote:

> [...] It would be nice to write it all in the Org file, yet for me such
> data shall better be in the database. And links are then copied from
> central place to Org files or any other files finally, or to email, or
> shared by SMS, or published as web pages when necessary.
>

I think you touch on a couple of interesting points here.

Firstly, it could be difficult to separate out a particular application
from one's Org usage overall.  For me, for the particular case of this
choir role, that is not the case; but I can see that it might be for
others.  I guess that means that the application will be better if it
doesn't force you to move your fundamental data into a form specifically
for that application, but is able to work well with data across your Org
usage as a whole.

Secondly, when one thinks this kind of thing through, it all boils down to
just two things
- tables of fundamental data
- code for operating on that data and generating summaries and derived
tables.
One might then think: why still be in Org mode?  As opposed to a
traditional database.  I think the answer, for me, is that keeping in Org
and plain text means that there are so many levels of possibility that I
can fall back on, if my coding and workflows turn out to be deficient in
some way.  Working in Emacs and Org mode just feels nice.  Also, in my
case, there isn't the massive scale that might motivate using a more
scalable database.

Best wishes,
    Neil

[-- Attachment #2: Type: text/html, Size: 2006 bytes --]

next prev parent reply	other threads:[~2019-09-10 21:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08 17:37 Best practice for providing an Org-based application? Neil Jerram
2019-09-08 19:57 ` Marcin Borkowski
2019-09-09  1:01 ` Bob Newell
2019-09-09 16:47 ` John Kitchin
2019-09-10 13:44   ` Jean Louis
2019-09-10 21:49     ` Neil Jerram [this message]
2019-09-11  7:11       ` Marcin Borkowski
2019-09-10 21:34   ` Neil Jerram
2019-09-10 23:11     ` John Kitchin
2019-09-11  7:13       ` Marcin Borkowski
2019-09-11  7:35         ` SYOGM Management
2019-09-11 13:58         ` Martin Alsinet
2019-09-18 19:02 ` Thorsten Jolitz

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='CAKuG=vvG7t4EcT4+mch_behRR49dqMxQW-WF0HWxm4pC4Koneg@mail.gmail.com' \
    --to=neiljerram@gmail.com \
    --cc=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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

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).