From: Samuel Loury <konubinix@gmail.com>
To: luke call <luke350@onemodel.org>, Robert Klein <roklein@roklein.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: "atomic knowledge" modeling tool
Date: Tue, 16 Feb 2016 15:14:52 +0100 [thread overview]
Message-ID: <87wpq4u4gz.fsf@gmail.com> (raw)
In-Reply-To: <56B0C94D.2040005@onemodel.org>
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
luke call <luke350@onemodel.org> writes:
> On 02/02/16 00:23, Robert Klein wrote:
[...]
>> As your 'product' is
>> not relevant to org-mode [....]
>
> I mentioned OM here only because I thought it of interest to
> org-mode users, which it evidently was to at least two who thanked me,
> and I answered their questions, in order not to be rude to them.
I also thank you for that :-). For the time being, I use org-mode
because of all the features it provides (clocking, reporting, literate
programming, publishing, etc...). I implement a GTD-like workflow in it
with an integrated pomodoro timer and it works like a charm.
Nevertheless, org-mode is rather slow when my todo.org file becomes
quite large (~20K lines).
Also, it is a real pain to implement a tool that uses its information
From in some other language than elisp. I have been trying for some time
to implement a competitor of MobileOrg with python-for-android/kivy and
the most difficult part is by far extracting the information out of the
.org files. Actually, I am no fall-backing on a client/server approach
in which emacs is the server, giving access to the org content.
I still like a lot the liberty of the "plain text approach" of
org-mode. It is VERY powerful, but it becomes a real problem when
needing to use that power without emacs.
I did not try onemodel yet, but it looks like it palliates those two
problems. I will definitely take a look at it.
Thank you again for sharing.
--
Konubinix
GPG Key : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-02-16 14:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 18:21 "atomic knowledge" modeling tool luke call
2016-01-31 12:32 ` Eric S Fraga
2016-02-01 22:15 ` luke call
2016-02-02 8:49 ` Eric S Fraga
2016-02-03 9:33 ` Marcin Borkowski
2016-02-03 14:47 ` luke call
2016-02-03 17:15 ` Bingo UV
2016-02-03 18:22 ` luke call
2016-01-31 15:37 ` Ramon Diaz-Uriarte
2016-02-01 21:25 ` luke call
2016-02-03 8:04 ` Ramon Diaz-Uriarte
2016-02-02 7:23 ` Robert Klein
2016-02-02 15:20 ` luke call
2016-02-16 14:14 ` Samuel Loury [this message]
2016-02-16 16:18 ` Eric S Fraga
2016-02-16 16:44 ` Nicolas Goaziou
2016-02-16 19:52 ` Eric S Fraga
2016-02-20 18:09 ` Samuel Loury
2016-02-21 11:21 ` Nicolas Goaziou
2016-02-22 9:04 ` Samuel Loury
2016-02-24 16:46 ` Eric S Fraga
2016-02-29 13:31 ` Samuel Loury
2016-03-06 19:26 ` Samuel Loury
2016-03-07 15:28 ` Eric S Fraga
2016-03-10 8:01 ` Samuel Loury
2016-03-18 21:44 ` 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=87wpq4u4gz.fsf@gmail.com \
--to=konubinix@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=luke350@onemodel.org \
--cc=roklein@roklein.de \
/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).