Blueprint assignments for “xfi”
This listing shows the assignment of work for blueprints currently associated with xfi. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
1 → 9 of 9 specifications | First • Previous • Next • Last |
Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
---|---|---|---|---|---|---|
5 Essential | Input system for mapping raw controls into understandable events | 0 Approved | 7 Good progress | David Schneider | ||
5 Essential | Base EditorObject class that every large object in a track extends | 3 Drafting | 7 Good progress | David Schneider | David Schneider | |
5 Essential | Base TrackSection class extending EditorObject that every track section extends | 3 Drafting | 7 Good progress | David Schneider | David Schneider | |
4 High | Algorithm for iterative hit checking each frame | 0 Approved | 7 Good progress | David Schneider | ||
4 High | Standard GUI objects extending Element | 3 Drafting | 0 Unknown | |||
3 Medium | Input configuration element | 3 Drafting | 0 Unknown | |||
3 Medium | Track Editor for xfi | 3 Drafting | 6 Slow progress | David Schneider | ||
2 Low | Generic, extendable file chooser gui object | 3 Drafting | 0 Unknown | |||
2 Low | Editor for materials | 3 Drafting | 0 Unknown |
1 → 9 of 9 specifications | First • Previous • Next • Last |