Eclipse Community Forums: Eclipse Platform » Why not port JasperReports over to Eclipse ?

Home » Eclipse Projects » Eclipse Platform » Why not port JasperReports over to Eclipse ?

Why not port JasperReports over to Eclipse ? [message #309263]

Fri, 20 October 2006 23:17

Eclipse User

Hi guys,

Why not Eclipse port JasperReports over ? BUT few things need to taking
care
off... like java.awt.Color, java2D... Nice if we able to create something
like
what GCJ had done, a mapper... awt.Color will actually map over to
graphics.Color
... and Java2D, I think that the most difficult part...

What you guys think ?

Thanks

Re: Why not port JasperReports over to Eclipse ? [message #309264 is a reply to message #309263]

Sat, 21 October 2006 04:29

Eclipse User

Hi,

What do you want us to do? Create a visual designer for Jasper in
Eclipse? If you need buisness reporting I'd say look at the BiRT
project. I use Jasper-Reports in all my RCP applications and design them
using iReport (which I don't like very much but it works). If you
suggest creating a project for a visual designer for eclipse I would
love to see such an opensource project (a closed source project already
exists http://www.jasperassistant.com/features.html)?

Tom

Ivan schrieb:
> Hi guys,
>
> Why not Eclipse port JasperReports over ? BUT few things need to taking
> care
> off... like java.awt.Color, java2D... Nice if we able to create
> something like
> what GCJ had done, a mapper... awt.Color will actually map over to
> graphics.Color
> .. and Java2D, I think that the most difficult part...
> What you guys think ?
>
> Thanks

Re: Why not port JasperReports over to Eclipse ? [message #309266 is a reply to message #309264]

Sat, 21 October 2006 09:14

Eclipse User

Hi,

thanks for your repply :-D
Actually... JasperReports engine will not work with SWT in Mac OS X
because of
of the threading problems... That is why it is nice if java.awt.Color and
Java2D
sections able to map back to SWT specific libraries....

I used iReport as well. I dont think designer are a big problem...
only the engine...

Thanks guys

Re: Why not port JasperReports over to Eclipse ? [message #309268 is a reply to message #309266]

Sat, 21 October 2006 15:12

Eclipse User

Hi Ivan,

what's the problem with Mac? I haven't ever used Jasper on Mac what's
the problem there. I successfully run RCP-Applications on Win32 and
Linux Gtk. To I might be interested because maybe next year we'll get a
customer where our application has to run on Mac OSX. I'd say it would
be better to fix the threading problem. Who is the culprit Eclipse or
Jasper?

Tom

Ivan schrieb:
> Hi,
>
> thanks for your repply :-D Actually... JasperReports engine will not
> work with SWT in Mac OS X because of
> of the threading problems... That is why it is nice if java.awt.Color
> and Java2D
> sections able to map back to SWT specific libraries....
>
> I used iReport as well. I dont think designer are a big problem... only
> the engine...
>
> Thanks guys
>
>

Re: Why not port JasperReports over to Eclipse ? [message #309273 is a reply to message #309268]

Sun, 22 October 2006 11:14

Eclipse User

well... I dont think Apple will fix the threading problems for MacOSX
10.3.x
from what I found out recently... only MacOSX10.4.x are fixed but I havent
try out yet... Not sure how good will it be... That is why you are not
able to
design Swing app in Eclipse for MacOSX... except the latest Eclipse with
MacOSX 10.4.x.. I'm not sure whether this only for Mac Intel or Mac PPC as
well...
not sure... of cause~ mapping will make JasperReports run in 10.3.x and
above :-P
I think that too much work to do....

well...

Re: Why not port JasperReports over to Eclipse ? [message #309275 is a reply to message #309273]

Sun, 22 October 2006 14:59

Eclipse User

Ivan schrieb:
> well... I dont think Apple will fix the threading problems for MacOSX
> 10.3.x
> from what I found out recently... only MacOSX10.4.x are fixed but I
> havent try out yet... Not sure how good will it be... That is why you
> are not able to
> design Swing app in Eclipse for MacOSX... except the latest Eclipse with
> MacOSX 10.4.x.. I'm not sure whether this only for Mac Intel or Mac PPC
> as well...
> not sure... of cause~ mapping will make JasperReports run in 10.3.x and
> above :-P
> I think that too much work to do....
> well...
>

So what you are saying is:
- Swing-Applications with JasperReports work in MacOSX
- SWT-Applications with JasperReports don't

So why Apple has to fix something, isn't SWT/eclipse the problem and has
to fix something? Are there any bug entries in bugzilla describing the
problem? Are those problems occuring if you don't open any Swing window
e.g. exporting directly to say PDF and then open Acroread?

The AWT stuff you are asking for is already ported although e.g. when we
talk about fonts SWT is not as flexible as AWT as I remember:

http://svn.sourceforge.net/viewvc/swingwt/swingwt/trunk/src/ swingwt/awt/

One would have to find out what needs to be done to make:
- JasperReport libs free from Swing and AWT components
- What's missing in swingwt and needs to be implementented

Please keep me informed about your findings and as already said creating
an opensource designer for JasperReports on Eclipse would be a really
really interesting project I'd like to contribute.

Tom

Re: Why not port JasperReports over to Eclipse ? [message #309282 is a reply to message #309275]

Mon, 23 October 2006 04:35

Eclipse User

Yes... JasperReports will work fine with Swing app but not SWT in MacOSX...

About the threading problem, u can refer to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=67384

and you will found out it's actually is Apple problems... They only patch
it
in MacOSX 10.4.x with JVM1.5.... but... not sure how stable it is... 1st
patch

This threading problem occur when you are refering to AWT methods or
objects
that need to access OS directly... eg, awt.Color and etc... it got nothing
to do with Swing or not... it is awt...

I found out swingwt didnt actually port awt.Color to swt yet... not a full
set
... but i think it is good if SwingWT can used JasperReports as a reference
or a test ground for this purpose...

About the designer... nice if we can just used SwingWT to compile iReport
into SWT app... instead of re-create the designer again... ehehe :-P

Ivan

Re: Why not port JasperReports over to Eclipse ? [message #309285 is a reply to message #309282]

Mon, 23 October 2006 07:04

Eclipse User

Hi,

well the thread you mention deals with embedding Swing-Apps in SWT_AWT
bridge but do you really need to do this with Jasper? I directly export
reports to PDF and don't need the SWT_AWT bridge.

Tom

Ivan schrieb:
> Yes... JasperReports will work fine with Swing app but not SWT in MacOSX...
>
> About the threading problem, u can refer to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=67384
>
> and you will found out it's actually is Apple problems... They only
> patch it
> in MacOSX 10.4.x with JVM1.5.... but... not sure how stable it is... 1st
> patch
>
> This threading problem occur when you are refering to AWT methods or
> objects
> that need to access OS directly... eg, awt.Color and etc... it got nothing
> to do with Swing or not... it is awt...
>
> I found out swingwt didnt actually port awt.Color to swt yet... not a
> full set
> .. but i think it is good if SwingWT can used JasperReports as a reference
> or a test ground for this purpose...
>
> About the designer... nice if we can just used SwingWT to compile
> iReport into SWT app... instead of re-create the designer again... ehehe
> :-P
>
> Ivan
>

Re: Why not port JasperReports over to Eclipse ? [message #309303 is a reply to message #309285]

Mon, 23 October 2006 21:27

Eclipse User

Hi,

You no need SWT_AWT component... but.. that bug explainted why SWT and
AWT crash together on MacOSX..

http://www.myeclipseide.com/index.php?name=PNphpBB2&file =viewtopic&t=12464&postdays=0&postorder=asc& start=0

You can generate the report into PDF BUT! the generate process must done
in
another non-SWT application, after that pass the URL to SWT app...
SWT application will not able to generate print file or compile any jrxml
into print file... because it needs to access java.awt.* and that will
cause SWT app crash in MacOSX....

Ivan

Previous Topic:	Common Navigator and default actions
Next Topic:	Dynamic Help Questions

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 11:00:46 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter