KS-Todo: CounterGUI

1 Requirements

This Feature Requests results from the todos of the Kitchen Sink Guideline: KS-Entry: Counter.

The Novelty and Status Counter need a corresponding UI Service class unifying their implementation. We propose to implement one abstract CounterGUI (name to be decided) base class with NoveltyCounterGUI and StatusCounterGUI as children using the same base class. The Glyph class should accept an instance of CounterGUI to be rendered next to the glyph. The impementation should restrict the usage of the classes according the the rules given in the entry listed above as much as reasonable. 

All existing instances of Novelty and Status Counter MUST follow the rules given in the entry listed above and use the CounterGUI instances along with the glyph class. If the Gyph class does not support a needed give, please write a comment here, so we can work on an improved Gyph Guideline. So far we found the following instances needing to be changed:

• The number for the Novelty Counter of the Comments Glyph can currently not be reduced even if the comments are consulted. They should be changed into the Status Counter. Better display all not consulted messages with the Novelty Counter and all other with the Status Counter.
• In ratings, the Novelty Counter is currently used to display the total amount of ratings, this should be done with a Status Counter.

2 Additional Information

• Idea / concept: (please add your name when creating this feature request)
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

4 Implementation

{please give a description of the final implementation and add screenshots if possible}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.