emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: colorg: Some news!
Date: Mon, 21 Jan 2013 10:53:29 -0500	[thread overview]
Message-ID: <86ehhe7csm.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <87obgjythf.fsf@casa.home> (daimrod@gmail.com's message of "Mon, 21 Jan 2013 06:50:52 +0100")

Daimrod <daimrod@gmail.com> writes:

> François Pinard <pinard@iro.umontreal.ca> writes:

>> ColOrg is a project about real-time collaborative editing of Org files.

> That's a really cool project!


> Do you plan to keep the server in Python?  Or do you think it would be
> possible to make this in Emacs Lisp only with Elnode[1] for the
> server-side?

Once we get a working solution, the protocol remains the contact point.
The server could be replaced using other languages, and new clients may
be written for other editors (given they are extensible enough).  My
goal is quickly getting something usable, so I selected the means that
looked fastest to me, and that's how Python got in the picture.

Is there any incentive for rewriting the server in Emacs Lisp?  For one,
even if rather bearable, Emacs Lisp is not my preferred programming
language.  Moreover, I consider a bit wrong having to rely on an editor
for tasks wholly unrelated to editing.  Other people are free to have
differing opinions, and do that rewrite, however. 

If I really had more time and less pressure, I would likely have
selected Node (JavaScript) to write the server instead of Python.  The
choice of JSON within the ColOrg communication protocol is a way, for
me, to leave that door opened.  One not so hidden dream is to bring Org
mode a bit closer to Web browsers, if there are ways to do so.


  reply	other threads:[~2013-01-21 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21  5:30 colorg: Some news! François Pinard
2013-01-21  5:50 ` Daimrod
2013-01-21 15:53   ` François Pinard [this message]
2013-01-21 16:28     ` Daimrod

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:

  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=86ehhe7csm.fsf@iro.umontreal.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=emacs-orgmode@gnu.org \


* 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


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