From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: org export Taskjuggler Date: Thu, 07 Feb 2013 16:13:50 +0530 Message-ID: <87mwvgpfo9.fsf@gmail.com> References: <876229nrxf.fsf@gmail.com> <1360081806.93848.YahooMailNeo@web29801.mail.ird.yahoo.com> <87vca6sktq.fsf@gmail.com> <87r4ksjug7.fsf@sbs.ch> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:45585) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3Oxj-0000aw-Mt for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 05:44:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U3Oxi-0006bd-1D for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 05:44:15 -0500 Received: from mail-pa0-f53.google.com ([209.85.220.53]:49398) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3Oxh-0006bG-R9 for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 05:44:13 -0500 Received: by mail-pa0-f53.google.com with SMTP id bg4so1318268pad.40 for ; Thu, 07 Feb 2013 02:44:12 -0800 (PST) In-Reply-To: <87r4ksjug7.fsf@sbs.ch> (Christian Egli's message of "Thu, 07 Feb 2013 11:21:12 +0100") 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: Christian Egli Cc: Yann Hodique , Org Mode List , Nicolas Goaziou Christian Egli writes: > Nicolas Goaziou writes: > >> If nothing has been started once the new export framework is installed >> and the early bugs are fixed, I will do the port. > > I don't quite understand why we need to "port" anything. The taskjuggler > exporter is different than the other exporters in that it doesn't really > export the content of an org file. Instead it just goes through the > headlines (using the mapping API), takes some to be tasks and reads the > properties of these headlines to build the taskjuggler file. It pretty > much ignores any text that is between the headlines (see also the > commentary in org-taskjuggler.el). In essence it treats the org file as > a tree of nodes with properties that define the tasks, resources and > reports. It doesn't use any of the common (old) exporting > infrastructure. So woudn't a "ported" org-taskjuggler.el look exactly > like to one that we have today? I am not working on Taskjuggler exporter. I do have a FreeMind exporter in the works. That said, moving the TaskJuggler exporter to new org-export-* APIs - Nicolas calls them tools - is "a good thing". Each new exporter, exercises or emphasizes different aspects of the export infrastructure. I am sure "porting" TaskJuggler will further solidify the org-export framework in terms of exposing existing bugs or adding new utilties or APIs. http://orgmode.org/worg/dev/org-export-reference.html If TaskJuggler exporter "just works", then it is good. The porting task can be done in an un-hurried manner. > Thanks > Christian --