From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org export Taskjuggler Date: Thu, 07 Feb 2013 14:13:26 +0100 Message-ID: <87lib0l11l.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]:54186) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3RIQ-0005Xf-WD for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 08:13:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U3RIP-0007Is-Hn for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 08:13:46 -0500 Received: from mail-we0-x235.google.com ([2a00:1450:400c:c03::235]:47349) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3RIP-0007Ik-BU for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 08:13:45 -0500 Received: by mail-we0-f181.google.com with SMTP id t44so2071151wey.40 for ; Thu, 07 Feb 2013 05:13:44 -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: Org Mode List , Yann Hodique Hello, 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. What it really exports isn't important. ox.el is a framework to export any part of an Org buffer (including non-contiguous parts like headlines only) to another format that can be, at least during an intermediary step, written as a string. In a export back-end, you basically specify an export action for each type of syntax. If nothing is provided, that the syntax will be ignored. In this case, the taskjuggler back-end would only provide a function for headlines. > It doesn't use any of the common (old) exporting > infrastructure. To be honest, I only gave it a cursory look, but it requires "org-exp" and uses a few functions from from it, like, e.g. `org-default-export-plist', `org-infile-export-plist', `org-install-letbind'. Some work needs to be done at this level. > So woudn't a "ported" org-taskjuggler.el look exactly > like to one that we have today? Externally, it would, hopefully. Internally, some changes are required. I also think it would much benefit from it, but I'm biased, obviously. Regards, -- Nicolas Goaziou