Bug 134022 - Usability of the Preview tab in the Eclipse Report Editor
Summary: Usability of the Preview tab in the Eclipse Report Editor
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 2.0.1   Edit
Assignee: Birt-ReportViewer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-30 03:56 EST by Pascal Ruault CLA
Modified: 2006-04-07 04:21 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Ruault CLA 2006-03-30 03:56:12 EST
I am using BIRT 1.0.1.

Here is the scenario I want to implement. I have an application that lets the user create a BIRT template using the Eclipse Report Editor. This template is connected to a custom data source provided by my application. I want the user to be able to preview the result in the Preview tab.

As far as I understood, the viewer embedded in the Preview tab is packaged as a web application and I have to copy my plug-ins in the directory ECLIPSE_HOME/plugins/org.eclipse.birt.report.viewer_1.0.1/birt/plugins to be able to make the Preview tab work with my custom data source.

The problem is that my data source is using a lot of plug-ins and copying 
all the plug-ins is not user friendly. I don't want my user everytime
he installs a fresh version of BIRT to copy all my plug-ins to preview
the template he just created with my custom data source.

I may have missed something but I read the documentation and went to the forums, 
but I cannot find a way not to copy all my plug-ins to use the viewer embedded 
in the Preview tab.

In an Eclipse context, the viewer should be aware of all the plug-ins 
used to launch Eclipse.
Comment 1 Wenfeng Li CLA 2006-04-06 22:41:09 EDT
this has been fixed in BIRT 2.0. and 2.1.  You no longer need to copy your plugins to the viewer subfolder.  Can you give the new version a try and let us know if it works for you?
Comment 2 Pascal Ruault CLA 2006-04-07 04:21:20 EDT
We haven't port our product to Eclipse 3.1.x. This is why we are using BIRT 1.0.1.
As soon as we will compatible with Eclipse 3.1 or higher, we will use BIRT 2.0 or higher and I will give a try.

Thanks