Talk:Round reform
From DPCanadaWiki
Contents |
DPToo from this perspective
Constraint 1: One round at a time
At any given time, all of a project's pages must be in the same round.
This constraint disappears.
No Rounds. Page workflow is determined by a Page Task Sequence template, wherein Tasks are associated and assigned a numerical Seqence value. Pages can advance from one task to another; or a constraint can be assigned to keep all Pages from the same Project at or below a Sequence value (effectively synchronizing their progress.)
Constraint 2: All pages the same
Over the lifetime of a project, all of its pages are proofed (once per round) in the same sequence of rounds.
This constraint disappears.
Constraint 3: Chain
For any given page, the proofings form a chain, with the output of one becoming the input of the next.
The pages single-step through the Tasks in DPToo, but independently. The same Task can be assigned a Repeat Count minimum, allowing Task repetitions. So this constraint disappears.
If simultaneous Tasks are desired, they can be assigned the same Sequence number. The code to merge the results has not been developed.
Constraint 4: States are Assigned, not Derived
There is currently a complex array of rules for assigning States to Projects (not Pages). This makes it impossible to determine the sequence of steps dynamically based on cumulative information.
Eliminating this "complex array of rules" was one of the primary requirements of DPToo, and it has been accomplished. The Task Sequence can be altered at any time. At this point it's manual; automation algorithms need to be specified, but would be easy to implement.
Discussion of alternatives
IMHO this discussion is still bound too tightly by the concepts built into the existing design. Note how often the word "round" occurs, when the point is that it shouldn't even have meaning.
