You are viewing a plain text version of this content. The canonical link for it is here.
Posted to portalapps-dev@portals.apache.org by "Gonzalo Aguilar (JIRA)" <ji...@apache.org> on 2010/03/19 19:48:27 UTC
[jira] Created: (APA-31) BIRT reporting portlet application
BIRT reporting portlet application
----------------------------------
Key: APA-31
URL: https://issues.apache.org/jira/browse/APA-31
Project: Portals Apps
Issue Type: New Feature
Environment: Linux azul1 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux
Java 1.5 -1.6
Wicket 1.4
BIRT 2.5.2
Reporter: Gonzalo Aguilar
Assignee: David Sean Taylor
A new set of portlet applications will be provided...
Up to now only two portlets are provided for this startup issue.
ChartViewer
ReportViewer
Both of them are exactly equal right now because. I mean I copied and pasted the code from one to the other to be able to hack ChartViewer after to find a way to render only a chart from a report design and be able to set width and height on the fly when rendering. That's the only cause to create a different portlet for Charting.
Right now it works well if resize should not be supported.
Current features are:
Full Wicket App
Two working modes [View, Edit]
[View Mode]
Report is generated on the fly.
Different reports can be shown with only one portlet (Via Edit
Mode).
Report parameters are used on report generation.
[Edit Mode]
Reports can be deployed directly using one directory. Drag &
Drop deploy... :-)
Custom preference panels are created on the fly based on report
parameters.
Report value for parameters are fetched from database
dynamically or statically on edit time. Depending on how report
is built.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (APA-31) BIRT reporting portlet application
Posted by "Gonzalo Aguilar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APA-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gonzalo Aguilar updated APA-31:
-------------------------------
Attachment: ScreenShot-JIRAISSUE-APA31.jpg
Screenshot showing various reports that only contains charts.
> BIRT reporting portlet application
> ----------------------------------
>
> Key: APA-31
> URL: https://issues.apache.org/jira/browse/APA-31
> Project: Portals Apps
> Issue Type: New Feature
> Environment: Linux azul1 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux
> Java 1.5 -1.6
> Wicket 1.4
> BIRT 2.5.2
> Reporter: Gonzalo Aguilar
> Assignee: David Sean Taylor
> Attachments: ScreenShot-JIRAISSUE-APA31.jpg
>
>
> A new set of portlet applications will be provided...
> Up to now only two portlets are provided for this startup issue.
> ChartViewer
> ReportViewer
> Both of them are exactly equal right now because. I mean I copied and pasted the code from one to the other to be able to hack ChartViewer after to find a way to render only a chart from a report design and be able to set width and height on the fly when rendering. That's the only cause to create a different portlet for Charting.
> Right now it works well if resize should not be supported.
> Current features are:
> Full Wicket App
> Two working modes [View, Edit]
>
> [View Mode]
> Report is generated on the fly.
> Different reports can be shown with only one portlet (Via Edit
> Mode).
> Report parameters are used on report generation.
>
> [Edit Mode]
> Reports can be deployed directly using one directory. Drag &
> Drop deploy... :-)
> Custom preference panels are created on the fly based on report
> parameters.
> Report value for parameters are fetched from database
> dynamically or statically on edit time. Depending on how report
> is built.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (APA-31) BIRT reporting portlet application
Posted by "Gonzalo Aguilar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APA-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gonzalo Aguilar updated APA-31:
-------------------------------
Attachment: ScreenShot-JIRAISSUE-APA31-EditMode.jpg
Edit Mode for report.
You can see the upper combo box where all reports in the webapp directory are shown. When you select a report the options below will change to reflect new report parameters.
In this case this report has 3 parameters. They were built using 2 dynamic lists and 1 static list. Which are currently supported for INTEGER, STRING, DECIMAL values. Not all tested though.
Everything is dynamic and customizable via BIRT. The panel will be built on the fly when report is loaded.
> BIRT reporting portlet application
> ----------------------------------
>
> Key: APA-31
> URL: https://issues.apache.org/jira/browse/APA-31
> Project: Portals Apps
> Issue Type: New Feature
> Environment: Linux azul1 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux
> Java 1.5 -1.6
> Wicket 1.4
> BIRT 2.5.2
> Reporter: Gonzalo Aguilar
> Assignee: David Sean Taylor
> Attachments: ScreenShot-JIRAISSUE-APA31-EditMode.jpg, ScreenShot-JIRAISSUE-APA31.jpg
>
>
> A new set of portlet applications will be provided...
> Up to now only two portlets are provided for this startup issue.
> ChartViewer
> ReportViewer
> Both of them are exactly equal right now because. I mean I copied and pasted the code from one to the other to be able to hack ChartViewer after to find a way to render only a chart from a report design and be able to set width and height on the fly when rendering. That's the only cause to create a different portlet for Charting.
> Right now it works well if resize should not be supported.
> Current features are:
> Full Wicket App
> Two working modes [View, Edit]
>
> [View Mode]
> Report is generated on the fly.
> Different reports can be shown with only one portlet (Via Edit
> Mode).
> Report parameters are used on report generation.
>
> [Edit Mode]
> Reports can be deployed directly using one directory. Drag &
> Drop deploy... :-)
> Custom preference panels are created on the fly based on report
> parameters.
> Report value for parameters are fetched from database
> dynamically or statically on edit time. Depending on how report
> is built.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.