From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: iOrg
Date: Fri, 16 Sep 2016 22:50:57 +0200 [thread overview]
Message-ID: <87intv7emm.fsf@gmail.com> (raw)
In-Reply-To: 87bmzpdpzz.fsf@alphapapa.net
Adam Porter <adam@alphapapa.net> writes:
Hi Adam,
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> [WARNING: this is an extremely long post with lots of boxquotes that
>> might turn out unreadable, you might want to consider this as spam
>> and just ignore it]
>
> Hi Thorsten,
>
> I guess I have missed iOrg before, because this looks very interesting!
> If I understand correctly, iOrg runs a web server written in PicoLisp
> which presents a set of Org files as an editable wiki in a browser?
iOrg is two things:
- the PicoLisp Wiki (which is a lightweight but complete application
with user-, role-, document-, version-management, authentication,
etc.) with Org-mode syntax, where you can create, edit and (full text)
search wiki pages as Org files that are stored as BLOBS in the
PicoLisp database and viewed as HTML in the browser.
- a database application that maps textbased Org-mode files to an
object-oriented class hierarchy, where each headline presents an
object (instance) of class +OrgHeadline, and each file presents an
object (instance) of class +OrgData, and the tree structure of an Org
file is represented by links between these objects.
> If so, this opens up a world of possibilities. Imagine having your
> personal Org files (at least, ones without very personal data) editable
> on your personal web server from any computer, even one without Emacs
> installed (including mobile devices)! You could edit your Org files
> from any system, then sync changes with Git when you get home and
> continue editing in Emacs.
From my point of view, Org-mode's greatest strength (being integrated in
powerful Emacs) is kind of a weakness too. Did you ever try to write Org
syntax without any editor support? Not very comfortable ... your idea
seems perfectly valid to me when its about editing the headline
properties of an +OrgHeadline object in the browser, but not so much for
writing lengthy an syntax rich content of a headline. There you really
need Emacs for editing ...
> I feel like I've seen a similar project before, one not based on
> PicoLisp...I think it ran from within Emacs...I'd have to google it up
> again. But I don't think it was nearly as advanced as this.
There are several Emacs Web Servers. They can't be as advanced as this
because they would have to compete with the PicoLisp application
programming framework and its underlying object-oriented lisp database,
which is a tough task.
> Anyway, if I could make one suggestion to help get things going again,
> it would be to add a bit more info to the readme so that visitors can
> immediately understand what it's about. :)
Thats a good suggestion, but actually I did not want that, because its a
bit too early. Its not yet version 0.9 for public announcement, maybe
0,8? I was surprised how good it worked yesterday, did not touch it for
a long time, there is not missing too much.
--
cheers,
Thorsten
next prev parent reply other threads:[~2016-09-16 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 11:34 iOrg (was: Programmatically handling org files) Philip Hudson
2016-09-14 22:06 ` iOrg Thorsten Jolitz
2016-09-15 17:36 ` iOrg Adam Porter
2016-09-16 20:50 ` Thorsten Jolitz [this message]
2016-09-17 15:15 ` iOrg Adam Porter
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=87intv7emm.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).