slaisne Posted April 3, 2007 Share Posted April 3, 2007 Hi all, iReport 1.3.2 is too slow than 1.3.1.I disable the magnet option, but same problem. Plateform: MacOsXJDK 1.5.0 Link to comment Share on other sites More sharing options...
slaisne Posted April 3, 2007 Author Share Posted April 3, 2007 same behavior on Windows XP + JDK 1.5.When I'm writing text in image expression text area, characters are display slowly Link to comment Share on other sites More sharing options...
raulinon Posted April 3, 2007 Share Posted April 3, 2007 What's your JRE version? Link to comment Share on other sites More sharing options...
slaisne Posted April 3, 2007 Author Share Posted April 3, 2007 Java5 Link to comment Share on other sites More sharing options...
hingerl Posted April 3, 2007 Share Posted April 3, 2007 hi, 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?? Link to comment Share on other sites More sharing options...
raulinon Posted April 3, 2007 Share Posted April 3, 2007 Try to download Java Runtime Environment Version 5.0 Update 11, and see what happen B) Link to comment Share on other sites More sharing options...
thork Posted April 3, 2007 Share Posted April 3, 2007 edit: Sorry, double-posted. Post edited by: thork, at: 2007/04/03 15:24 Link to comment Share on other sites More sharing options...
thork Posted April 3, 2007 Share Posted April 3, 2007 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. Link to comment Share on other sites More sharing options...
slaisne Posted April 3, 2007 Author Share Posted April 3, 2007 I'm trying to install jre 1.5.0-11 and test again. Link to comment Share on other sites More sharing options...
Giulio Toffoli Posted April 3, 2007 Share Posted April 3, 2007 This version of iReport is slow not for the graphics, but because the report is verified in background if modified in the last 5 seconds. I'll add an option to disable this feature that can be very heavy on old systems. Giulio Link to comment Share on other sites More sharing options...
thork Posted April 4, 2007 Share Posted April 4, 2007 Thanks giulio, that would be an excellent help. Link to comment Share on other sites More sharing options...
slaisne Posted April 4, 2007 Author Share Posted April 4, 2007 Thanks too giulio Link to comment Share on other sites More sharing options...
Giulio Toffoli Posted April 4, 2007 Share Posted April 4, 2007 Changes committed in the repository giulio Link to comment Share on other sites More sharing options...
mlehnert Posted April 12, 2007 Share Posted April 12, 2007 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 Link to comment Share on other sites More sharing options...
jmaher Posted April 19, 2007 Share Posted April 19, 2007 I submitted a bug: Slow Element Selection: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? Link to comment Share on other sites More sharing options...
Giulio Toffoli Posted April 19, 2007 Share Posted April 19, 2007 I missed to ship the new groovy jar. The problem is fixed in the repository (where you can find the new groovy jar). about the new performace, I'll do some extra profiling. Thanks a lot! Giulio Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now