Reorganize/Refactor ItemFormPanel
GENERAL
TESTING
GENERAL
TESTING
Description
is depended on by
Activity

Jon Gorrono April 12, 2012 at 7:55 PM
No. And if you plan to go through all the unresolved tickets and ask the same question, the answer is "no" wrt them as well

Peter Peterson April 12, 2012 at 4:31 PM
Is this complete?
Thomas Amsler September 8, 2011 at 3:09 PM
Estimate: 20 SP
Thomas Amsler May 23, 2011 at 10:55 AM
Besides refactoring the ItemFormPanel, we also need a workflow, which helps configure the proper UI state after each event (button clicks, check boxes, user input).
e.g.
User creates an extra credit category. As soon as the user toggles the extra credit category check box, the UI needs to consistently represent what fields/actions are available in that specific state. In this specific case, we need to gray out the drop lowest field, etc.
The ItemFormPanel is currently very complex and in that complexity is danger, especially in making changes.
Since the form does more than just "items", I propose we break it up into:
CategoryFormPanel - Handles editing/creation of categories
GradebookFormPanel - Handles editing of the gradebook itself
AssignmentFormPanel - Handles editing/creation of GB assignments