[piccolo2d-dev] Issue 190 in piccolo2d: Move to version 1.6 as minimum JDK requirement for piccolo-core
Status: New Owner: New issue 190 by heue...@gmail.com: Move to version 1.6 as minimum JDK requirement for piccolo-core http://code.google.com/p/piccolo2d/issues/detail?id=190 Issue 152 and Issue 153 (and possibly Issue 117) require version 1.6 of the JDK. Creating a separate issue to track this future change, after which the changes from those issues may be merged into core. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 152 in piccolo2d: Refactor PPath to use Path2D on JDK 1.6+
Comment #10 on issue 152 by heue...@gmail.com: Refactor PPath to use Path2D on JDK 1.6+ http://code.google.com/p/piccolo2d/issues/detail?id=152 Created a separate issue 190 to track jdk 1.6 changes to core. In the meantime, I would like to create a separate module on trunk called jdk16 that will contain the code from the ppath-refactoring branch in a new package org.piccolo2d.nodes.jdk16 -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] new module jdk16 on trunk
As mentioned in issues 152 and 153, I would like to create a separate module on trunk called jdk16 that will contain the code from the ppath-refactoring branch in a new package org.piccolo2d.nodes.jdk16 This new module will require JDK 1.6 as a minimum, whereas core, swt, examples, and swt-examples will still require JDK 1.5. I suppose there might also be a jdk16-examples module. I'll wait a few days for comment before committing to trunk. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 153 in piccolo2d: PArea, a wrapper for java.awt.geom.Area to allow Constructive Area Geometry (CAG) operations
Comment #9 on issue 153 by heue...@gmail.com: PArea, a wrapper for java.awt.geom.Area to allow Constructive Area Geometry (CAG) operations http://code.google.com/p/piccolo2d/issues/detail?id=153 Created a separate issue 190 to track jdk 1.6 changes to core. In the meantime, I would like to create a separate module on trunk called jdk16 that will contain the code from the ppath-refactoring branch in a new package org.piccolo2d.nodes.jdk16 -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 185 in piccolo2d: Memory leak - PActivityScheduler keeps processed activities in reference
Comment #10 on issue 185 by heue...@gmail.com: Memory leak - PActivityScheduler keeps processed activities in reference http://code.google.com/p/piccolo2d/issues/detail?id=185 Is there any reason that ArrayList processingActivities needs to exist at all? Cannot processActivities iterate in reverse over the activities in activities directly? -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 187 in piccolo2d: general shapes are not filled correctly under SWT
Updates: Status: Accepted Labels: Type-Defect Priority-High Effort-Low OpSys-All Toolkit-Piccolo2D.Java Component-SWT Milestone-1.3.1 Comment #2 on issue 187 by heue...@gmail.com: general shapes are not filled correctly under SWT http://code.google.com/p/piccolo2d/issues/detail?id=187 (No comment was entered for this change.) -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 188 in piccolo2d: wrong line width when drawing general shapes under SWT
Updates: Status: Accepted Labels: Type-Defect Priority-High Effort-Low OpSys-All Toolkit-Piccolo2D.Java Component-SWT Milestone-1.3.1 Comment #1 on issue 188 by heue...@gmail.com: wrong line width when drawing general shapes under SWT http://code.google.com/p/piccolo2d/issues/detail?id=188 (No comment was entered for this change.) -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 189 in piccolo2d: Provide advanced graphical options under SWT
Updates: Status: Accepted Labels: Type-Enhancement Priority-Medium Effort-Medium Toolkit-Piccolo2D.Java OpSys-All Component-SWT Milestone-1.3.1 Comment #1 on issue 189 by heue...@gmail.com: Provide advanced graphical options under SWT http://code.google.com/p/piccolo2d/issues/detail?id=189 If these changes can be made without breaking binary compatibility, and I haven't fully reviewed them yet, then they can go into the 1.3.1 milestone. If not, they will have to wait for 2.0. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 180 in piccolo2d: Drawing tears when dragging or resizing path nodes
Comment #7 on issue 180 by heue...@gmail.com: Drawing tears when dragging or resizing path nodes http://code.google.com/p/piccolo2d/issues/detail?id=180 Issue 184 has been merged into this issue. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 184 in piccolo2d: visual artifacts when rendering (node disapearance, ghosts, etc)
Updates: Status: Duplicate Mergedinto: 180 Comment #7 on issue 184 by heue...@gmail.com: visual artifacts when rendering (node disapearance, ghosts, etc) http://code.google.com/p/piccolo2d/issues/detail?id=184 Thank you for your review. Closed as duplicate of issue 180. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException
Comment #8 on issue 164 by heue...@gmail.com: PNode#moveToFront change to avoid java.util.ConcurrentModificationException http://code.google.com/p/piccolo2d/issues/detail?id=164 OK if we mark as WontFix then? -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 178 in piccolo2d: PNode.SetPaint() is not working (SWT version)
Updates: Status: Invalid Comment #2 on issue 178 by heue...@gmail.com: PNode.SetPaint() is not working (SWT version) http://code.google.com/p/piccolo2d/issues/detail?id=178 (No comment was entered for this change.) -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 103 in piccolo2d: PInputEventFilter is Overly Complex
Comment #1 on issue 103 by heue...@gmail.com: PInputEventFilter is Overly Complex http://code.google.com/p/piccolo2d/issues/detail?id=103 I also dislike PInputEventFilter. Consider UnaryPredicateK and related from Apache Commons Functor http://commons.apache.org/sandbox/functor/apidocs/index.html and/or PredicateT and related from Google Collections/Guava http://guava-libraries.googlecode.com/svn/trunk/javadoc/index.html -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
