Project

General

Profile

Actions
Copy link

Bug #3635

closed

Create ReportItem Type Hierarchy

Added by debi staggs about 16 years ago. Updated over 15 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
debi staggs
Category:
reporting
Target version:
SanParksRelease
Start date:
11/12/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3635

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)
Actions
Copy link
 #1

Updated by debi staggs about 16 years ago

Each report item implementation should be responsible for rendering it's values.

Actions
Copy link
 #2

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.

Actions
Copy link
 #3

Updated by ben leinfelder over 15 years ago

not a 2a1-critical bug. leaving in sanparks release

Actions
Copy link
 #4

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.

Actions
Copy link
 #5

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 3635

Actions
Copy link

Also available in: Atom PDF