[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #26 on issue 43 by mr0...@mro.name: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 repairing one broken link with another - sorry. ( mind the "CSV" link bottom right on the issues listing at http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3#For_the_Release_Notes ) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #25 on issue 43 by mr0...@mro.name: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 (mind the "CSV" link bottom right on the issues listing at http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3#For_the_Release_Notes) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #24 on issue 43 by mr0...@mro.name: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Releasenote issue list: For http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3#For_the_Release_Notes I'd even just go with copying http://code.google.com/p/piccolo2d/issues/csv? can=1&q=Milestone%3A1.3%20status%3DVerified&colspec=ID%20Type%20Component%20Summary&sort=%20co mponent%20-type%20-summary -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #23 on issue 43 by re...@colorado.edu: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 I moved the PSwing-specific discussion to new issue #144, and will create new tickets for outstanding issues as we look into them. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #22 on issue 43 by mr0...@mro.name: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 @Sam: Please file new issues rather than adding them to this one. If the problems from #19 persist, can you open issues for them, please. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #21 on issue 43 by allain.lalonde: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 After further consideration, I have rolled back all changes to the way PSwing paints and sizes itself. It was a breaking change and the simplest way of getting it back into a state that's compatible with 1.2.1 is to revert. Let me know if the simulations have reverted to the way they worked before. http://code.google.com/p/piccolo2d/source/detail?spec=svn811&r=809 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #20 on issue 43 by allain.lalonde: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Thank you very much for responding! I hope that we can work together to resolve your problems. To shed some light on the changes that were made. #1 and #2 stem from the work and subsequent workarounds to Issue 83. It seems that by painting to an image, rather than to the graphics context directly, the effects of antialiasing on the length of the rendered text were ignored by certain JComponents. If anti-aliasing is taken into account, it seems that the text is slightly larger but the bounds are not, causing swing to draw the same text, in the same shape with ellipsis. Rather than continue double buffering a push was made to disable them and try to get to fix the ellipse problems. Until now, we thought those fixes had worked. Apparently not. The modifications in reshape are an attempt to rule out some obvious ellipsis causing things, like the rendering a JLabel narrower than it's reported minimum width including its insets. In a further attempt to rule out some strange Graphics2D miscalculations of text widths, I'd added a enforceNoEllipsis method that measures the minimum allowable size for JLabel and JButtons given the font metrics of the current Graphics2D object. What happens if you run your tests with the render quality set to LOW? As for #3 and #4, wth? I'll try to write some stress tests for PSwing since it appears that our current examples aren't cutting it. I'm hesitant to roll back all of the changes, but I'll more than gladly do so if nothing turns up. Once again, thanks for getting back to us. I apologize for any inconvenience this is causing your team. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #19 on issue 43 by re...@colorado.edu: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Here are some issues my coworker identified in his projects by updating from piccolo 1.2.1 to the current r772 of piccolo. These issues were produced on Mac, we need to see if they are problematic on other platforms as well. Our next steps will be to create self-contained minimal test cases to isolate each issue: (1) Extra whitespace around components (usually buttons). Caused by PSwing.reshape change, need to ask Piccolo team why they changed this. Problem occurs in almost all sims, haven't verified a workaround, workaround will likely need to be applied everywhere. (2) ellipsis in labels and radio buttons. Occurs in many sims, might be Mac only? (3) PSwing doesn't paint contents of a JPanel. Eg, animation control in acid-base. No idea why, no workaround identified. (4) PNodes that aren't fully painted (eg, tools in glaciers). No idea why, no workaround identified. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #18 on issue 43 by heuermh: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 I added an Issues section to http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3. There are a few issues left to triage, a few new issues left to review, and a ton of fixed issues left to verify. Feel free to move those around on the wiki page as necessary. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #17 on issue 43 by mr0...@mro.name: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 BTW - created a wiki page to collect the todos to rel. 1.3. Should the list entries there http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3 rather be issues filed? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #16 on issue 43 by allain.lalonde: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 I thought I hadn't changed the strategy, but of course I might be wrong. Can you confirm that it wasn't just the big in Issue 137 causing it to misbehave? Thank you. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #15 on issue 43 by re...@colorado.edu: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 It also looks like the default toImage fill strategy changed between r390 and r689, many of our toImage results are showing up differently. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #14 on issue 43 by re...@colorado.edu: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 I created issue #137 to track one of the new rendering problems: http://code.google.com/p/piccolo2d/issues/detail?id=137 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #13 on issue 43 by mr0...@mro.name: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Hi Sam, if the current trunk causes rendering problems v1.2.1 didn't that's a showstopper for 1.3. Can you give us a hint how to reproduce the problem - at best opening an issue. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #12 on issue 43 by heuermh: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Yes, by all means, if you find difference in behavior between 1.2.1 and svn trunk, please submit issues against Milestone 1.3. All the refactoring and cleanup going on lately shouldn't have left trunk in an inconsistent state at any point. I can remember only a one or two specific revisions that broke the build or failed any unit tests. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #11 on issue 43 by allain.lalonde: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Piccolo is undergoing a cleanup, and in the process, it's quite possible thatsome things have broken (probably by my hand). I'd tried to push the code coverage up before doing anything too drastic, but it seems some things have broken. Could you please perform a git-bisect or equivalent to try and determine exactly which revision broke it, and tell me the kinds of nodes that are broken for you? Would you mind opening an issue with the specific details of your environment and the problem that's occurring. Much appreciated, and my apologies, Allain. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #10 on issue 43 by re...@colorado.edu: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 My team and I had been using a copy of piccolo's r390 and when I tried upgrading to r689 I noticed a few rendering problems; some nodes don't appear, some are the wrong size, etc. I was wondering if piccolo trunk/head was in an inconsistent state or in the middle of a significant refactor, or if it's appropriate for me to to use r700 or so to try to identify and possibly resolve these issues. I'm thinking it would be best to look into these issues before a public release of 1.3, for our project and others that might have similar issues. Please let me know what you think. Thanks, Sam Reid -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #9 on issue 43 by mr0...@mro.name: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 I agree with Michael. As to issue 63 I'd assign it to 1.4 as well as issue 122. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #8 on issue 43 by heuermh: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 I wouldn't feel comfortable with trunk going out as version 1.2.2, as nearly every line of source has been touched since then. How about we triage the 1.3 issues? Must go in 1.3 Issue 124 Issue 128 Should go in 1.3 Issue 70 Issue 109 Issue 126 I am comfortable pushing all of the following issues to 1.4. They are all waiting further comment or review. Issue 10 Issue 16 Issue 18 Issue 19 Issue 24 Issue 26 Issue 27 Issue 30 Issue 31 Issue 33 Can Issue 63 be marked as WontFix? Issue 122 still needs initial evaluation. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #7 on issue 43 by samrreid: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Since the 1.3 timeframe is looking like it might be a long ways off, I'm wondering how stable the svn trunk is, or about the possibility of making a 1.2.2 release candidate before focusing on the 1.3 release? I'd prefer not to use svn trunk in my production code if at all possible (a released version seems less risky), but I'd like to benefit from several of the recent fixes since 1.2.1. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #6 on issue 43 by heuermh: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 There is no timeline for the 1.3 release. I see 15 open issues against Milestone:1.3, in order for a 1.3 release to happen all of those issues need to be resolved or pushed off to a later Milestone. There are also a few new issues without a Milestone set that should probably go with 1.3. Patches welcome. :) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #5 on issue 43 by akurtakov: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Is there some planned timeframe for the 1.3 release? Or I should just use trunk? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #4 on issue 43 by akurtakov: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Depends on swt 2.* was mentioned as a problem of the latest release. There are still problems with swt compilation. See http://code.google.com/p/piccolo2d/issues/detail?id=125 for details and patch. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #3 on issue 43 by heuermh: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Eliminate dependency on sun.* classes in PFixedWidthStroke is Issue 48. Added the post to piccolo-dev as Issue 124. Could you create a new issue for "depends on swt 2.*"? I'm not a SWT developer, so I don't know why that might be a problem. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #1 on issue 43 by akurtakov: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Are there plans for making this release soon? Version 1.2.1 is really showing it's age nowadays: * uses sun.dc.* packages - not usable with OpenJDK * depends on swt 2.* Even if there are some unfinished things, it will really help having a release usable in modern environments. P.S. I found this while looking at the latest release of pydev.sf.net which carryies some snapshot of piccolo(local changes?) and builds them as part of its build. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 43 in piccolo2d: Prepare the 1.3 release
Comment #2 on issue 43 by akurtakov: Prepare the 1.3 release http://code.google.com/p/piccolo2d/issues/detail?id=43 Also can you consider adding the code used in pydev? It was sent to piccolo list long ago. See https://mailman.cs.umd.edu/pipermail/piccolo-chat/2006/003452.html -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
