[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=1q=Milestone%3A1.3%20status%3DVerifiedcolspec=ID%20Type%20Component%20Summarysort=%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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 -~--~~~~--~~--~--~---
[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 -~--~~~~--~~--~--~---
