3 Aug 2005 17:57
3 Aug 2005 18:29
Legend for the symbols used in the HTML reports?
Hi,
I'm back with some more questions, I'm afraid.
The HTML reports are a great feature of taskjuggler.
However, I don't really understand the precise meaning of the all the colours and symbols used.
Some are obvious:
Green = past work on task-overview
Red = future work on task-overview
<> Milestone
== continuation of something
Some are less obvious. So this is some guesswork
v= start of a task with subtasks
=v end of a task with subtasks
[= start of a task without subtasks
=] end of a task without subtasks
Green: task with sufficient resources (on task-details)
the number states the amount of effort invested (?).
Red: task with insufficient resources (on task-details) if before 'NOW', otherwise planned effort
the number states the amount of resources missing (?) or effort planned.
(Continue reading)
3 Aug 2005 18:40
Re: Resources: new employees / quiting employees in middle of project
Hi Chris, I found a minute to spare. This is a draft addition for the vacation property. I hope you can use it. You suggested I work with diff. But on what file? I downloaded the manual-svn. I see a whole bunch of folders and files, but don't know what to do next. I found an XML file with the property reference, but not the examples. If you're fine with receiving the occasional suggestion in flat file form, then there is no problem. If you want me to use diff, please give me some more detailed instructions on what to do. Download the manual tar, unpack it. And then? Do a 'make' on something? Then work with diff on the result? I started learning to work with the command line, but haven't gotten very far yet. Kind regards, Hdk -- http://www.taskjuggler.org/manual-svn/property_vacation_reso urce.html project simple "Simple Project" "1.0" 2005-06-06 2005-06-26 resource tux "Tux" { #Tux will be on holiday in March vacation 2005-03-11 - 2005-03-17 }(Continue reading)
3 Aug 2005 19:45
Re: Legend for the symbols used in the HTML reports?
You are pretty close. The symbols are all correct and try to model the graphical elements of a typical GANTT chart. You are slightly off with respect to the colours: green: Completed work red: Not yet completed work The color is based on the current date (or 'now') or the 'complete' value specified. And you are also correct about the manual. This is not documented anywhere yet. Chris -- TaskJuggler Developer
3 Aug 2005 21:07
4 Aug 2005 10:10
4 Aug 2005 17:24
Re: Big project: define html reports in a common file for all projects?
h_dk wrote on Thu, 04 August 2005 07:46
> Hi Chris,
> Current working directory should be the directory of the calling file, not the directory of the included
file.
>
> I'll see if upgrading fixes this.
That is unlikely. I've just looked at the 2.1.1 code in Report::open():
QString absFileName = fileName;
// Check if the fileName is not an absolute file name.
if (fileName[0] != '/')
{
// Prepend the path of the file where the report was defined, so
// relative report file names are always interpreted relative to
// their definition.
QString path;
if (defFileName[0] == '/')
path = defFileName.left(defFileName.findRev('/', -1) + 1);
absFileName = path + fileName;
}
f.setName(absFileName);
This is how the include mechanism work in other places. I'm not sure if this is the wisest thing to do, but I
hesitate to change this behavior without very good reason as it would break compatibility with older versions.
But making the report definition a macro and calling it with a parameter for the file name should work in your
case. But keep in mind that if it's not an absolute file name, the current working directory of the file
where the report is defined will be prepended. In case of a macro this is the macro call, not the macro definition.
(Continue reading)
4 Aug 2005 18:04
4 Aug 2005 18:38
Re: Big project: define html reports in a common file for all projects?
Quote: > Quote: > > Hi Chris, > > Current working directory should be the directory of the calling file, not the directory of the included file. > > > > I'll see if upgrading fixes this. > > > That is unlikely. I've just looked at the 2.1.1 code in Report::open(): > ... Sorry, I didn't mean this as a statement of how it ought to work. This is what I understand from the following sentence in the manual: Includes the specified file name as if its contents would be written instead of the include property. I think I just found the exception that confirms the rule. :) Quote: > This is how the include mechanism work in other places. I'm not sure if this is the wisest thing to do, but I hesitate to change this behavior without very good reason as it would break compatibility with older versions. I'm not a programmer, so I can't give you advice. But you must have guessed that by now. :d Do you have any idea why the XML report behaves differently from the HTML reports? Quote: > But making the report definition a macro and calling it with a parameter for the file name should work in your case. But keep in mind that if it's not an absolute file name, the current working directory of the file(Continue reading)
4 Aug 2005 22:17
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"
}
]
(Continue reading)
RSS Feed