Re: [O] org export Taskjuggler
Nicolas Goaziou n.goaz...@gmail.com 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? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] org export Taskjuggler
Christian Egli christian.e...@sbs.ch writes: Nicolas Goaziou n.goaz...@gmail.com 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 --
Re: [O] org export Taskjuggler
Hello, Christian Egli christian.e...@sbs.ch writes: Nicolas Goaziou n.goaz...@gmail.com 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
Re: [O] org export Taskjuggler
Hello, Giovanni Ridolfi giovanni.rido...@yahoo.it writes: - Messaggio originale - Da: Nicolas Goaziou n.goaz...@gmail.com Inviato: Domenica 3 Febbraio 2013 20:00 2. As a consequence, three export back-ends are not available anymore: Taskjuggler, XOXO and Docbook. Are there any plans to have a taskjuggler export compatible with the new exoprt framework? Yes. This one has a high priority tag put on it. If not, is there a way I can help/contribute? I think, but I may be wrong, that Jambunathan has started something in the area. You may get in touch with him. If nothing has been started once the new export framework is installed and the early bugs are fixed, I will do the port. But, obviously, I'll appreciate if Someone beats me to it. Regards, -- Nicolas Goaziou
