From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Smithline Subject: Re: Google Summer of Code -- 3 Org projects for our first participation! Date: Sat, 28 Apr 2012 19:30:23 -0400 Message-ID: <4F9C7D8F.7040408@neilsmithline.com> References: <8762cpad2q.fsf@gnu.org> <4F9653BD.7030201@wilkesley.net> <87obqh8s6m.fsf@googlemail.com> <4F98A7F0.6080405@neilsmithline.com> <87mx5zrklf.fsf@altern.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33159) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SOH5y-0004xQ-Ot for emacs-orgmode@gnu.org; Sat, 28 Apr 2012 19:30:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SOH5w-00062E-Pe for emacs-orgmode@gnu.org; Sat, 28 Apr 2012 19:30:30 -0400 Received: from mail-qa0-f41.google.com ([209.85.216.41]:40261) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SOH5w-000625-LH for emacs-orgmode@gnu.org; Sat, 28 Apr 2012 19:30:28 -0400 Received: by qabg27 with SMTP id g27so1094553qab.0 for ; Sat, 28 Apr 2012 16:30:26 -0700 (PDT) In-Reply-To: <87mx5zrklf.fsf@altern.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org I think I'm lacking sufficient information to fully understand the situation (that's just a secret code for saying I'm confused). From your original email about GSOC: On 4/24 01:55 , Bastien wrote: > As part of the engineering process, abstract out a > web-framework (called iOrg) based on these GNU Emacs technologies. A > web-framework written in Elisp, with Org files used for database > functionality, is a new approach that enables interactive web > applications built on top of GNU Emacs. Bugpile is an example > application, but useful in itself. To me, that sounds like iOrg will be an Emacs web server or an Emacs plugin to a web server or something like that. In reply to my email you wrote: On 4/26 03:57 , Bastien wrote: > As I understand it, iOrg will convert .org files to HTML using the > internal Org's HTML exporter. I don't see how github could use such > a setup to produce HTML files from Org (unless github runs an Emacs > batch query for exporting HTML... which seems very unlikely - and > wrong by design anyway. To me, that sounds like iOrg will not be appropriate to be part of a web server. Hence, I'm confused. My guess is that I'm confused about the exact nature of iOrg as I was surprised that someone was going to turn Emacs into something appropriate to be part of a Github web server. Even factoring in a large college hacker coding multiplier, three months seemed too short to me. That was part, albeit the smaller part, of my motivation for trying to put aside bugpile in favor of just iOrg. I will follow-up with my thoughts about the org-ruby gem in a separate email. Neil Neil Smithline http://www.neilsmithline.com Proud GNU Emacs user since 1986, v. 18.24. On 4/26 03:57 , Bastien wrote: > Hi Neil, > > Neil Smithline writes: > >> I've run into this problem dealing with the weak presentation of Org Mode >> files on Github. Github uses the Ruby gem org-ruby >> (https://github.com/bdewey/org-ruby) to convert .org files to HTML. I've >> added a feature or two to org-ruby but really feel that trying to >> completely re-implement Org Mode in a Ruby gem is a losing battle. > > What will help org-ruby (and github's support of org files) is to > stabilize the syntax of .org files as much as possible. We are > currently working in this direction. > > org-ruby's main job is to convert .org files into HTML or textile files. > >> If I understand the project correctly, a working iOrg could be used to >> support Github's rendering of .org files. Github could just drop the use of >> org-ruby and use iOrg as an external converter for formatting .org files. > > As I understand it, iOrg will convert .org files to HTML using the > internal Org's HTML exporter. I don't see how github could use such > a setup to produce HTML files from Org (unless github runs an Emacs > batch query for exporting HTML... which seems very unlikely - and > wrong by design anyway. > > Let's see how iOrg evolves but let's stick to the bugpile for now. > > If the list can specifically help about org-ruby issues, let's help! > > All best, > >> PS: And the answer is "Yes. I am aware that vehemently suggesting a project >> is equivalent to offering to help with it." :-D > > Good :) >