MantisBT - Scoring Application Prototype
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000009Scoring Application Prototype[All Projects] Generalpublic2014-05-14 00:442014-05-28 16:35
Reporterptrue 
Assigned Toptrue 
PrioritynormalSeverityfeatureReproducibilityalways
StatusresolvedResolutionwon't fix 
PlatformOSOS Version
Product Version 
Target VersionSprint #5Fixed in VersionSprint #5 
Summary0000009: Combine actions and commands
DescriptionTry to combine UI actions and Document command classes so that we don't need to create two classes for each command.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-05-14 00:44ptrueNew Issue
2014-05-14 00:44ptrueStatusnew => assigned
2014-05-14 00:44ptrueAssigned To => ptrue
2014-05-14 02:02administratorTarget Version => Sprint 0000004
2014-05-14 02:04administratorStatusassigned => new
2014-05-22 22:49administratorStatusnew => assigned
2014-05-22 22:49administratorTarget VersionSprint 0000004 => Sprint 0000005
2014-05-28 16:35ptrueNote Added: 0000021
2014-05-28 16:35ptrueStatusassigned => resolved
2014-05-28 16:35ptrueFixed in Version => Sprint 0000005
2014-05-28 16:35ptrueResolutionopen => won't fix

Notes
(0000021)
ptrue   
2014-05-28 16:35   
Looks like this is not a good idea.
AppAction has only one instance per application. This instance is added to the menu and to the toolbar if needed.
Instance of the DocumentCommand is created every time the command is executed. This instance is stored to the history and its undo/redo methods are called when needed.
Therefore combining these types would be unnatural and would bring many problems.