Hi all,
iReport 1.3.2 is too slow than 1.3.1.
I disable the magnet option, but same problem.
Plateform: MacOsX
JDK 1.5.0
iReport 1.3.2 is too slow than 1.3.1.
I disable the magnet option, but same problem.
Plateform: MacOsX
JDK 1.5.0
15 Answers:
Posted on April 3, 2007 at 2:30pm
hi,
i think, it´s the "new" feature
http://sourceforge.net/project/shownotes.php?release_id=498385&group_id=64348
maybe there´s a switch to turn off this feature??
i think, it´s the "new" feature
* New error handler to easily find and prevent report errors |
http://sourceforge.net/project/shownotes.php?release_id=498385&group_id=64348
maybe there´s a switch to turn off this feature??
Posted on April 3, 2007 at 3:22pm
I ended up with the same experience slaisne is having. The new colors and handles in iReport 1.3.2 are pretty and nifty, but I'm getting 4-5 second wait times when I do anything, even something as small as moving a textbox from one location to another. My workstation is slow and old to start with, but I'm seeing a large speed difference between 1.3.2 and 1.3.1. iReport 1.3.1 is not blazingly quick on my workstation, but it moves at an acceptable pace.
I'm not complaining here -I appreciate the work that's gone into iReport in all of its incarnations. I'm just corroborating slaisne's findings with my own. I'll continue to use 1.3.1 until I can get my workstation upgraded (unlikely) or there's reason to believe 1.3.2 works a lot faster for me than it is now.
In case it matters, I'm running Windows XP SP2 with JDK 1.6.0 and JRE 1.6.0.
I'm not complaining here -I appreciate the work that's gone into iReport in all of its incarnations. I'm just corroborating slaisne's findings with my own. I'll continue to use 1.3.1 until I can get my workstation upgraded (unlikely) or there's reason to believe 1.3.2 works a lot faster for me than it is now.
In case it matters, I'm running Windows XP SP2 with JDK 1.6.0 and JRE 1.6.0.
Posted on April 12, 2007 at 4:36pm
Hi,
first of all as this is my first post here: Great work. I appreciate this very much.
As I also recognized the preformance drawbacks in 1.3.2 I checked out your latest changes in the repository and built a new version. If I disable the real time validation feature now the performance is a bit better but far from 1.3.1. And also the report elements (e.g. fields) are no longer marked with the red border if they are moved out of the band.
Furthermore I saw that your update to groovy is not in 1.3.2. There still is "groovy-all-1.0-beta-10.jar" in the downloadable src-zip. Why is that?
Regards,
Marc
first of all as this is my first post here: Great work. I appreciate this very much.
As I also recognized the preformance drawbacks in 1.3.2 I checked out your latest changes in the repository and built a new version. If I disable the real time validation feature now the performance is a bit better but far from 1.3.1. And also the report elements (e.g. fields) are no longer marked with the red border if they are moved out of the band.
Furthermore I saw that your update to groovy is not in 1.3.2. There still is "groovy-all-1.0-beta-10.jar" in the downloadable src-zip. Why is that?
Regards,
Marc
Posted on April 18, 2007 at 5:45pm
I submitted a bug:
Slow Element Selection:
[url=http://jasperforge.org/sf/go/artf2213]artf2213
Would this be the cause of my issue as well? I don't think however that by clicking on an element that it should reverify the code? Or maybe the verification takes a few seconds so it almost never finishes by the time the next 5 seconds has passed since the first verification, so it is always verifying, causing slow selection?
Slow Element Selection:
[url=http://jasperforge.org/sf/go/artf2213]artf2213
Would this be the cause of my issue as well? I don't think however that by clicking on an element that it should reverify the code? Or maybe the verification takes a few seconds so it almost never finishes by the time the next 5 seconds has passed since the first verification, so it is always verifying, causing slow selection?