[O] OT: taskjuggler question [was: Re: taskjuggler (tj3) export issues and proposals]
I hope you'll excuse the off-topic noob question: I (think I) installed tj3.1 per the official instructions. I get $ tj3 --version TaskJuggler v3.1.0 - A Project Management Software I can export the example org file that Christian sent out to a tjp, process it to Plan.html from the command line and the html file looks OK afaict, so the basics seem to be in place. But I have no TaskJugglerUI executable, which seems to be what the exporter tries to call for export-and-open (C-c C-e J): what am I missing? Thanks, Nick
Re: [O] OT: taskjuggler question [was: Re: taskjuggler (tj3) export issues and proposals]
On Thu, Feb 2, 2012 at 10:08 AM, Nick Dokos nicholas.do...@hp.com wrote: I hope you'll excuse the off-topic noob question: I (think I) installed tj3.1 per the official instructions. I get $ tj3 --version TaskJuggler v3.1.0 - A Project Management Software I can export the example org file that Christian sent out to a tjp, process it to Plan.html from the command line and the html file looks OK afaict, so the basics seem to be in place. Did you tweak =org-export-taskjuggler-default-reports= variable? What report definition exists in your resultant .tjp? Mine fails with the default setting in org-taskjuggler.el. But I have no TaskJugglerUI executable, which seems to be what the exporter tries to call for export-and-open (C-c C-e J): what am I missing? Nothing wrong. There currently is no UI for tj3. The original org exporter was designed for 2.4.3 which did have a UI. The new workflow (unless they come up with a new UI) is: org - C-e j - tj3 file.tjp - view output report Best regards, John Thanks, Nick
Re: [O] OT: taskjuggler question
Nick Dokos nicholas.do...@hp.com writes: But I have no TaskJugglerUI executable, which seems to be what the exporter tries to call for export-and-open (C-c C-e J): what am I missing? The TaskJugglerUI exists only if you have taskjuggler2.4 installed. The exporter predates tj3 and naively assumes that there is a TaskJugglerUI executable. It should really invoke a browser on the resulting HTML report[1] when you call export-and-open, at least when you are targeting tj3. The worst part is that it doesn't even tell the user that something failed, as it invokes the executable asynchronously using start-process-shell-command (info: (elisp) Asynchronous Processes). That way you can continue to work with emacs but emacs doesn't know what happened to the subprocess. I'll have to do some more research on how to start a process in the background and still check if it succeeded. Thanks Christian Footnotes: [1] the tricky bit here is of course to find the resulting HTML, as the name of it is defined in a tj3 report definition. I'd rather refrain from parsing these report definitions just to find the name of the HTML file to open. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] OT: taskjuggler question
Christian Egli christian.e...@sbs.ch wrote: Nick Dokos nicholas.do...@hp.com writes: But I have no TaskJugglerUI executable, which seems to be what the exporter tries to call for export-and-open (C-c C-e J): what am I missing? The TaskJugglerUI exists only if you have taskjuggler2.4 installed. The exporter predates tj3 and naively assumes that there is a TaskJugglerUI executable. It should really invoke a browser on the resulting HTML report[1] when you call export-and-open, at least when you are targeting tj3. The worst part is that it doesn't even tell the user that something failed, as it invokes the executable asynchronously using start-process-shell-command (info: (elisp) Asynchronous Processes). That way you can continue to work with emacs but emacs doesn't know what happened to the subprocess. I'll have to do some more research on how to start a process in the background and still check if it succeeded. --8---cut here---start-8--- (setq p (start-process-shell-command foo nil foo)) #process foo (process-status p) exit (process-exit-status p) 127 --8---cut here---end---8--- Thanks Christian Footnotes: [1] the tricky bit here is of course to find the resulting HTML, as the name of it is defined in a tj3 report definition. I'd rather refrain from parsing these report definitions just to find the name of the HTML file to open. Yup - a pain. Maybe ask for an option to tj3: $ tj3 --silent --spit-out-name-of-html-file foo.tjp Plan.html or $ tj3 --silent --symlink-report-to foo.html foo.tjp and you can go after foo.html - but of course this assumes that you have symlinks. Nick
