Bug 223130 - Composite Component
Summary: Composite Component
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Birt-Report-inbox@eclipse.org CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2008-03-18 17:06 EDT by Scott Rosenbaum CLA
Modified: 2008-03-18 18:39 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Rosenbaum CLA 2008-03-18 17:06:13 EDT
This is similar to 213204, but different.

I would like to be able to build a plug-in that defines composite components which uses standard ReportItems and combines them, adding properties and containment (slot) relations.  In addition to control over properties, I would like to be able to add/modify the pages in the PropertyEditor.  Finally, I would like to be able to tie the component to Wizard Pages to help manage the properties/containment relationships.

I have three use cases:

1) Simple DataItem Extension
Currently there is only one data item for all data types.  In some environments I would like to support multiple data items that are specific to the type of data: currency, integer, string, etc.  In that way I can drag and drop from the palette and in one step avoid several programming clicks.

2) Table In Table
A common development theme is to have a table inside of a table.  While relatively easy to build now, it still requires some knowledge and skill to complete.  This type of extension would populate a wizard when dragged to the report which would assist the user in the creation of the table in table structure.  

3) Page Styles
The ability to drag and drop multiple page styles into the Page Slot.

While simlar to the library element this is different in a couple of key ways.  

First, a library element has references back to the parent object which can be over-ridden (sometimes by mistake).  This means that changes to the parent may not cascade to the children.  With this mechanism, the definition of the item would be in the plug-in which would set its own default values.

Second, there is no easy way to add library elements to the palette.  I have discussed this with Wenben and Ivy (at EclipseCon) and I think they understand what I hope to add.