Re: [Planner Dev] cost of tasks with subtasks

[Lincoln Phipps <lincoln phipps openmutual net>]

Richard Hult wrote:

> We really should turn the cost into a regular property, it's a bit weird
> to keep such an integral part as a custom property. This should be
> pretty easy since it's actually a regular property in the xml files. The
> database backend could be trickier, but at this stage I'm don't all
> opposed to just break the database, since it has never been really
> official (we didn't even ship the database scheme...). If it can be
> changed without breakage that's good of course.

The current database scheme has a std_rate in the resource table.
This is a real and is read in as a gfloat.

We are using the current cost as this anyway i.e. standard rate for
the typical  '8' hour working day.

> In the meantime, we could add a small hack that just listens to changes
> to that particular custom property.
>
> /Richard