From: h_dk (hanneloredk_at_yucom.be)
Date: Thu Aug 04 2005 - 22:17:11 CEST
From: h_dk <hanneloredk@yucom.be> Message-Id: <20050804201711.510F02730445@einstein.suse.de> Date: Thu, 4 Aug 2005 22:17:11 +0200 (CEST) Subject: [taskjuggler] Re: Big project: define html reports in a common file for all projects!
Hi,
Just FYI, this is how I got it to work.
First I had some trouble with using macro's defined in an included file.
I looked at the manual under macro, but didn't find any info there.
I happened to look at the manual page on include again, and there found something about macro's in include files.
Quote:
> For technical reasons you have to supply the optional pair of curly brackets if the include is followed immediately by a macro that is defined within the included file.
Bingo! It might be a good idea to put this info on the macro page too.
Quote:
> If you define a macro in an include file, you must supply the optional pair of curly brackets after the include property, especially if the macro is called directly after the included file.
Next, I took my common file with the specifications for the html reports, and just encased each of them in a macro:
macro StaffOverview [
htmlresourcereport "Staff-Overview.html" {
${navbar}
columns no, name, scenario, weekly, effort
scenarios plan, delayed
loadunit hours
headline "Weekly working hours for the Project"
}
]
Even without passing the absolute path to the macro, the html reports are now suddenly created in the project folder, just like I wanted.
Excellent! Thanks for the pointer, Chris.
The manual doesn't really talk about handling Big Projects with Taskjuggler just now. I'm afraid I don't have the time to write this chapter either.
But it might be a good idea to include this trick in the Big Project example that is provided with Taskjuggler.
hdk
-- To unsubscribe, email the address listed in the List-Unsubscribe header For additional commands, email: taskjuggler-help@suse.com
This archive was generated by hypermail 2.1.7 : Thu Aug 04 2005 - 22:17:16 CEST