Bug #3635
closedCreate ReportItem Type Hierarchy
0%
Description
Create a type hierarchy for Report Items. It may look something like this:
Dynamic Items
ValueItem,
StringItem
ListItem
MatrixItem
TableItem
Reference Items
FileItem (text, .pdf, html, etc.)
Static items : definition does not require Provenance to look up the value.
hr, static text, page break, etc.
ImageItem (.png, .jpg., .gif)Updated by debi staggs about 16 years ago
Each report item implementation should be responsible for rendering it's values.
Updated by ben leinfelder over 15 years ago
I think it will be very useful to make StaticReportItem subclasses - if only to make rendering them in the UI more straightforward. The current use of "types" for the Static Item is workable for a small/controlled number of items, but requires quite a few changes to accommodate new types.
Updated by ben leinfelder over 15 years ago
not a 2a1-critical bug. leaving in sanparks release
Updated by debi staggs over 15 years ago
I am closing this bug, since this was created quite some time ago, although it did not look like the original hierarchy that was proposed. At this time the hierarchy looks something like this:
Item
DynamicReportItem
StaticReportItem
StaticReportItemImage, StaticReportItemLabel, etc.
Thinking that we might add 'view' classes to this as well.