[piccolo2d-dev] Re: [piccolo2d-users] Java API documentation not available on website ...
Hello Patrick, The URL below is actually for the source of the web pages checked into the subversion repository. These are/were exported and rsynced to the server that actually hosts the documentation at e.g. http://www.piccolo2d.org/doc/piccolo2d.java/release-3.0/core/overview-summary.html However, and I just noticed this yesterday, www.piccolo2d.org is not responding to requests. There is an issue here about webhosting that needs to be followed up on https://code.google.com/p/piccolo2d/issues/detail?id=248 michael On Thu, Jul 31, 2014 at 10:20 AM, patrickjphilips via Piccolo2D Users piccolo2d-us...@googlegroups.com wrote: Hi everyone, I don't know whether this is the correct place to post this, but it was the only one that seemed right; anyway I have just been to the new website https://piccolo2d.googlecode.com/svn/site/learn/api.html and could not access the Java API documentation. It appears to be displaying the source code rather than the pages. If I need to set some options in my browsers for this new site (although I did try with both IE explorer and Mozilla) would someone please let me know? Thanks. Patrick. -- You received this message because you are subscribed to the Google Groups Piccolo2D Users group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-users+unsubscr...@googlegroups.com. To post to this group, send email to piccolo2d-us...@googlegroups.com. Visit this group at http://groups.google.com/group/piccolo2d-users. For more options, visit https://groups.google.com/d/optout. -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [piccolo2d-dev] Copyright question.
Hello Stefan, You may use and redistribute in source and binary forms, with or without modification, as long as you meet the conditions of the license. If you make any modifications to the source that you find might be useful to others, we would encourage you to contribute those back to the project, but that is not a condition of the license. Cheers, michael On Wed, Jun 4, 2014 at 12:42 PM, Stefan Vahlgren stefan.vahlg...@gmail.com wrote: Hi. I am planning to use Piccolo2D as a graphics engine in a future commercial product. I will extend class org.piccolo2d.nodes.PShape in order to get the extra support I need in my own shapes. Is this ok, or am I violating the copyright by any means? I've attached the copyright comments (from class org.piccolo2d.nodes.PPath) below: /* * Copyright (c) 2008-2012, Piccolo2D project, http://piccolo2d.org * Copyright (c) 1998-2008, University of Maryland * All rights reserved. * * Redistribution and use in source and binary forms, with or without modification, are permitted provided * that the following conditions are met: * * Redistributions of source code must retain the above copyright notice, this list of conditions * and the following disclaimer. * * Redistributions in binary form must reproduce the above copyright notice, this list of conditions * and the following disclaimer in the documentation and/or other materials provided with the * distribution. * * None of the name of the University of Maryland, the name of the Piccolo2D project, or the names of its * contributors may be used to endorse or promote products derived from this software without specific * prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A * PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR * TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF * ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[piccolo2d-dev] Piccolo2D.Java related libraries
All, Now that version 3.0 has been released, I was able to release several Piccolo2D.Java related libraries to the Maven Central repository. http://search.maven.org/#search|ga|1|g%3A%22org.dishevelled%22 I have used these in various data visualization applications over the years (including the game engine-inspired ones). Piccolo2D easing activities and supporting classes. http://www.dishevelled.org/piccolo-ease Piccolo2D views for event lists. http://www.dishevelled.org/piccolo-eventlist-view Piccolo2D nodes for identifiable beans. http://www.dishevelled.org/piccolo-identify Piccolo2D particle system physics integration. http://www.dishevelled.org/piccolo-physics Piccolo2D ribbon nodes and supporting classes. http://www.dishevelled.org/piccolo-ribbon Piccolo2D sprite nodes and supporting classes. http://www.dishevelled.org/piccolo-sprite Piccolo2D state machine sprite and supporting classes. http://www.dishevelled.org/piccolo-state-machine-sprite Piccolo2D tile map nodes and supporting classes. http://www.dishevelled.org/piccolo-tilemap Piccolo2D venn diagram nodes and supporting classes. http://www.dishevelled.org/piccolo-venn The last one for example is used in this Venn and Euler diagram app for Cytoscape http://apps.cytoscape.org/apps/vennandeulerdiagrams (in an odd twist of dependencies, early versions of Cytoscape itself were built on Piccolo) michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] [ANNOUNCE] Piccolo2D.Java version 3.0 released
Piccolo2D.Java version 3.0 has been released and will be synced to the Maven Central repository shortly. http://code.google.com/p/piccolo2d/source/browse#svn%2Fpiccolo2d.java%2Ftags%2Fpiccolo2d-complete-3.0 Major changes: The minimum JDK version is now 1.6. JDK 1.6-only modules jdk16 and jdk16-examples have been merged to core and examples respectively. Piccolo2D.Java version 3.0 is _not_ binary compatible with version 1.3.x or version 2.x. Fixed and verified issues: 166 Refactor PNode.moveToBack() and related 190 Move to version 1.6 as minimum JDK requirement for piccolo-core 252 Merge build-related changes from trunk to branches/3.0-spike On behalf of the Piccolo2D developers, michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: Remove voting requirements from release process, was Re: [VOTE] Release Piccolo2D.Java 3.0-beta1-rc1
All, I have completed the following [x] remove voting requirements from ReleaseChecklist wiki page [x] update Maven plugin dependency versions [x] release the contents of branches/release-1.3 as version 1.3.2-rc1 [x] release the contents of trunk as version 2.0-rc1 [x] release the contents of branches/3.0-spike as version 3.0-beta1-rc2 [x] release the contents of branches/release-1.3 as version 1.3.2 [x] release the contents of trunk as version 2.0 [x] release the contents of branches/3.0-spike as version 3.0 [x] branch trunk to branches/release-2.0 [x] merge branches/3.0-spike to trunk [x] removed abandoned branches [x] updated wiki Readme [x] updated wiki ReleaseNotes [x] updated milestones for issue tracker [x] removed featured tag from 1.3.1 downloads At this point there are open issues for the 1.x and 2.x branches but I consider them no longer active. Development towards a future 3.1 release will proceed on svn trunk or on github as necessary. Cheers, michael On Tue, Nov 26, 2013 at 5:17 PM, Michael Heuer heue...@gmail.com wrote: All, I have completed the following [x] remove voting requirements from ReleaseChecklist wiki page [x] update Maven plugin dependency versions [x] release the contents of branches/release-1.3 as version 1.3.2-rc1 [x] release the contents of trunk as version 2.0-rc1 [x] release the contents of branches/3.0-spike as version 3.0-beta1-rc2 In one week if there are no issues with the release candidate versions, I will release the actual versions (1.3.2, 2.0, and 3.0-beta1) and then continue with - branch trunk to branches/release-2.0 - merge branches/3.0-spike to trunk - release the contents of trunk as version 3.0-beta1 If anyone thinks that I should just cut 3.0 at that time instead of 3.0-beta1 I would be fine with that too. michael On Thu, Nov 21, 2013 at 4:51 PM, Michael Heuer heue...@gmail.com wrote: All, I would like to propose removing the voting requirements from the Piccolo2D release process Votes from Piccolo2D project committers are binding, however votes from other contributors and users are welcomed. The vote must receive at least three +1 binding votes and no -1 binding votes. http://code.google.com/p/piccolo2d/wiki/ReleaseChecklist I was not able to recruit the necessary number of votes in April and the number of active committers has not improved since then. I will proceed-until-veto starting next week with the following: - remove voting requirements from ReleaseChecklist wiki page - update Maven plugin dependency versions - release the contents of branches/release-1.3 as version 1.3.2 - release the contents of trunk as version 2.0 - branch trunk to branches/release-2.0 - merge branches/3.0-spike to trunk - release the contents of trunk as version 3.0 Then at that point I may import trunk into a github repository and continue development on version 3.x there. Now would be a good time to raise objections. michael On Fri, Apr 19, 2013 at 4:41 PM, Michael Heuer heue...@gmail.com wrote: All, I was afraid this might happen . . . we don't have much going on with Piccolo2D these days and I probably won't be able to find three active committers to vote on a release. Since this is not the most significant release, just a release candidate for a beta, I propose to proceed-until-veto next week. michael On Wed, Apr 10, 2013 at 3:59 PM, Michael Heuer heue...@gmail.com wrote: On Wed, Apr 10, 2013 at 3:58 PM, Michael Heuer heue...@gmail.com wrote: This is a vote for releasing Piccolo2D.Java 3.0-beta1 based on release candidate rc1 (version 3.0-beta1-rc1). 3.0-beta1-rc1 is available from the Maven central repository (or will be shortly) at e.g. dependency groupIdorg.piccolo2d/groupId artifactIdpiccolo2d-core/artifactId version3.0-beta1-rc1/version /dependency --- [X] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] [ANNOUNCE] Piccolo2D.Java version 1.3.2-rc1 released
Piccolo2D.Java version 1.3.2-rc1 has been released and will be synced to the Maven Central repository shortly. http://code.google.com/p/piccolo2d/source/browse#svn%2Fpiccolo2d.java%2Ftags%2Fpiccolo2d-complete-1.3.2-rc1 Fixed and verified issues: 134 PTransformActivity can throw null pointer exception 207 Horizontal scrolling causes an exception 208 Merge maven reporting plugin versions to parent pom 211 Consider using Sonatype oss-parent-7.pom as the parent of parent/pom.xml 224 Update maven-site-plugin version to 3.0, remove maven-3 profile 229 Consider updating maven-checkstyle-plugin to version 2.8 230 Add link to Autocad DXF File Viewer on applications page 231 Mistake in java doc comment 235 PSwingEventHandler doesn't dispatch events to nodes at extreme scales 242 Typo in API docs 250 Update junit dependency version to 4.11 If no problems are found with -rc1 in the next week a proper 1.3.2 release will be made. On behalf of the Piccolo2D developers, michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] [ANNOUNCE] Piccolo2D.Java version 2.0-rc1 released
Piccolo2D.Java version 2.0-rc1 has been released and will be synced to the Maven Central repository shortly. http://code.google.com/p/piccolo2d/source/browse#svn%2Fpiccolo2d.java%2Ftags%2Fpiccolo2d-complete-2.0-rc1 Major changes: The root package name for Piccolo2D.Java is now org.piccolo2d to match the project domain name. The minimum JDK version is now 1.5. JDK 1.6-only code has been added to new modules jdk16 and jdk16-examples. Piccolo2D.Java version 2.0 is _not_ binary compatible with version 1.3.x. Fixed and verified issues: 33 PSwing components not visible in testing frameworks 37 change namespaces to piccolo2d, 86 inconsistencies of position method in PNode 135 Constants are not constant in the core. 136 PNotificationCenter is a singleton but isn't declared as final 152 Refactor PPath to use Path2D on JDK 1.6+ 153 PArea, a wrapper for java.awt.geom.Area to allow Constructive Area Geometry (CAG) operations 172 Add getRoot method to POffscreenCanvas 177 When deleting a selected node using the keyboard DEL a selection change is not fired 180 Drawing tears when dragging or resizing path nodes 186 Create a new package org.piccolo2d.examples.bugs or .issues 236 Add zoom event handler that responds to mouse wheel events 251 Merge build-related changes from release-1.3 branch to trunk If no problems are found with -rc1 in the next week a proper 2.0 release will be made. On behalf of the Piccolo2D developers, michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: Remove voting requirements from release process, was Re: [VOTE] Release Piccolo2D.Java 3.0-beta1-rc1
All, I have completed the following [x] remove voting requirements from ReleaseChecklist wiki page [x] update Maven plugin dependency versions [x] release the contents of branches/release-1.3 as version 1.3.2-rc1 [x] release the contents of trunk as version 2.0-rc1 [x] release the contents of branches/3.0-spike as version 3.0-beta1-rc2 In one week if there are no issues with the release candidate versions, I will release the actual versions (1.3.2, 2.0, and 3.0-beta1) and then continue with - branch trunk to branches/release-2.0 - merge branches/3.0-spike to trunk - release the contents of trunk as version 3.0-beta1 If anyone thinks that I should just cut 3.0 at that time instead of 3.0-beta1 I would be fine with that too. michael On Thu, Nov 21, 2013 at 4:51 PM, Michael Heuer heue...@gmail.com wrote: All, I would like to propose removing the voting requirements from the Piccolo2D release process Votes from Piccolo2D project committers are binding, however votes from other contributors and users are welcomed. The vote must receive at least three +1 binding votes and no -1 binding votes. http://code.google.com/p/piccolo2d/wiki/ReleaseChecklist I was not able to recruit the necessary number of votes in April and the number of active committers has not improved since then. I will proceed-until-veto starting next week with the following: - remove voting requirements from ReleaseChecklist wiki page - update Maven plugin dependency versions - release the contents of branches/release-1.3 as version 1.3.2 - release the contents of trunk as version 2.0 - branch trunk to branches/release-2.0 - merge branches/3.0-spike to trunk - release the contents of trunk as version 3.0 Then at that point I may import trunk into a github repository and continue development on version 3.x there. Now would be a good time to raise objections. michael On Fri, Apr 19, 2013 at 4:41 PM, Michael Heuer heue...@gmail.com wrote: All, I was afraid this might happen . . . we don't have much going on with Piccolo2D these days and I probably won't be able to find three active committers to vote on a release. Since this is not the most significant release, just a release candidate for a beta, I propose to proceed-until-veto next week. michael On Wed, Apr 10, 2013 at 3:59 PM, Michael Heuer heue...@gmail.com wrote: On Wed, Apr 10, 2013 at 3:58 PM, Michael Heuer heue...@gmail.com wrote: This is a vote for releasing Piccolo2D.Java 3.0-beta1 based on release candidate rc1 (version 3.0-beta1-rc1). 3.0-beta1-rc1 is available from the Maven central repository (or will be shortly) at e.g. dependency groupIdorg.piccolo2d/groupId artifactIdpiccolo2d-core/artifactId version3.0-beta1-rc1/version /dependency --- [X] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Remove voting requirements from release process, was Re: [VOTE] Release Piccolo2D.Java 3.0-beta1-rc1
All, I would like to propose removing the voting requirements from the Piccolo2D release process Votes from Piccolo2D project committers are binding, however votes from other contributors and users are welcomed. The vote must receive at least three +1 binding votes and no -1 binding votes. http://code.google.com/p/piccolo2d/wiki/ReleaseChecklist I was not able to recruit the necessary number of votes in April and the number of active committers has not improved since then. I will proceed-until-veto starting next week with the following: - remove voting requirements from ReleaseChecklist wiki page - update Maven plugin dependency versions - release the contents of branches/release-1.3 as version 1.3.2 - release the contents of trunk as version 2.0 - branch trunk to branches/release-2.0 - merge branches/3.0-spike to trunk - release the contents of trunk as version 3.0 Then at that point I may import trunk into a github repository and continue development on version 3.x there. Now would be a good time to raise objections. michael On Fri, Apr 19, 2013 at 4:41 PM, Michael Heuer heue...@gmail.com wrote: All, I was afraid this might happen . . . we don't have much going on with Piccolo2D these days and I probably won't be able to find three active committers to vote on a release. Since this is not the most significant release, just a release candidate for a beta, I propose to proceed-until-veto next week. michael On Wed, Apr 10, 2013 at 3:59 PM, Michael Heuer heue...@gmail.com wrote: On Wed, Apr 10, 2013 at 3:58 PM, Michael Heuer heue...@gmail.com wrote: This is a vote for releasing Piccolo2D.Java 3.0-beta1 based on release candidate rc1 (version 3.0-beta1-rc1). 3.0-beta1-rc1 is available from the Maven central repository (or will be shortly) at e.g. dependency groupIdorg.piccolo2d/groupId artifactIdpiccolo2d-core/artifactId version3.0-beta1-rc1/version /dependency --- [X] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [piccolo2d-dev] Re: [VOTE] Release Piccolo2D.Java 3.0-beta1-rc1
Hello John, Version 1.3.1 is the latest release in the 1.x branch. Work towards version 2.0 (jdk 1.5+) is on svn trunk but has not had any releases. Work towards version 3.0 (jdk 1.6+) is on the 3.0-spike branch and has had only the 3.0-beta1-rc1 release so far. I use 3.0-beta1-rc1 for all my downstream work and would recommend using that release if you are comfortable with the jdk 1.6+ requirement. As you may have noticed from this thread we as a development team have lost the momentum necessary to get releases out. michael On Fri, Aug 30, 2013 at 8:24 AM, jmsoft jms...@xs4all.nl wrote: Hello, I am currently using piccolo2d version 1.3.1. Where can I find/how can I get the latest official version? Thanks in advance. Kind regards, John Meertens Michael Heuer schreef op 2013-04-10 22:59: On Wed, Apr 10, 2013 at 3:58 PM, Michael Heuer heue...@gmail.com wrote: This is a vote for releasing Piccolo2D.Java 3.0-beta1 based on release candidate rc1 (version 3.0-beta1-rc1). 3.0-beta1-rc1 is available from the Maven central repository (or will be shortly) at e.g. dependency groupIdorg.piccolo2d/**groupId artifactIdpiccolo2d-core/**artifactId version3.0-beta1-rc1/**version /dependency --- [X] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... michael -- -- -- Piccolo2D Developers Group: http://groups.google.com/** group/piccolo2d-dev?hl=enhttp://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscribe@**googlegroups.compiccolo2d-dev%2bunsubscr...@googlegroups.com . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: draft road map
All, Given that there has been little to no contribution to Piccolo2D.Java recently and I personally am only interested in the 3.0-spike branch, I would like to revise a proposal from last year: On Tue, Sep 4, 2012 at 1:17 PM, Michael Heuer heue...@gmail.com wrote: 1.3.1 branch: Verify issues Fixed for Milestone 1.3.2 http://code.google.com/p/piccolo2d/issues/list?can=1q=label%3AMilestone-1.3.2%20status%3AFixed Triage issues Accepted or Started for Milestone 1.3.2 http://code.google.com/p/piccolo2d/issues/list?can=2q=Milestone%3D1.3.2+colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Find a release manager for 1.3.2 release Waiting on a release manager. 2.0 svn trunk: Resolve minimum JDK requirement for version 2.0 http://code.google.com/p/piccolo2d/issues/detail?id=190 Verify issues Fixed for Milestone 2.0 http://code.google.com/p/piccolo2d/issues/list?can=1q=label%3AMilestone-2.0+status%3AFixedcolspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Triage issues Accepted or Started for Milestone 2.0 http://code.google.com/p/piccolo2d/issues/list?can=2q=Milestone%3D2.0+colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Triage issues in New status for inclusion in a version 2.0 beta http://code.google.com/p/piccolo2d/issues/list?can=2q=status%3ANew+Toolkit%3DPiccolo2D.Java+colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Find a release manager for 2.0-beta1 release Waiting on a release manager. 3.0 Create a new branch branches/3.0-spike and mirror on github Set minimum JDK version to 1.6 or 1.7 Refactor jdk16 and jdk16-examples back to core and examples respectively This has been completed. I plan to update the build to use newer maven plugins and to cut a 3.0-beta1 release shortly. 4.0 Create a new branch branches/4.0-spike and mirror on github Refactor core APIs to have no dependencies on java.awt.* or javax.swing.* Refactor core implementation classes into at least two new modules (one Java2D plus POffscreenCanvas, one Java2D plus Swing (current PCanvas event support)) Spike on refactoring SWT, adding new Processing, Android modules Branch has been created but no further work has been completed. If anyone is interested in volunteering for the release manager role for version 1.3.2 or 2.0-beta1, please do so. michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [piccolo2d-dev] PIccolo2D.Java from Jython
Trevor Bekolay tbeko...@gmail.com wrote: I'm in the process of converting an existing Java program made with Piccolo2D to be written in Jython. In order to get familiar with interacting with Piccolo2D from Jython, I rewrote the examples from the Piccolo2D website to use Jython. I've put them up at https://github.com/tbekolay/piccolo2d-jython-examples; feel free to use them for whatever you'd like, if you think including the examples with Jython is helpful. Cool, thanks for the link. We have an applications built on Piccolo2D page here http://piccolo2d.org/applications/index.html or if there is somewhere else on piccolo2d.org or the code.google.com/p/piccolo2d wiki where you would like to see a mention, send a patch or let me know and you can be added as a project contributor. michael -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] remove PFrame full screen and PSwing FEST unit tests
Hello, Would anyone mind if I remove the full screen unit test from PFrame (PFrameTest.testFullScreenModeInstallsEscapeListeners), the PSwing FEST unit tests (PSwingFESTTest), and the external dependency on FEST? In my experience these unit tests are not reliable; sometimes they fail because of focus changes, sometimes the mouse cannot be captured, and sometimes the full screen mode fallback code doesn't work (i.e. works fine on my laptop but not when external monitor is attached). michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] PStyledText in Piccolo2D.NET
Hello Evan, That is great, let us know if we can help with the java side of things. Patches welcome, and if you send too many, we will ask if you want to be a committer. :) michael On Thu, Nov 8, 2012 at 5:26 AM, Evan Williams e...@my-technicolour-dreams.com wrote: Thanks Michael. I'm making reasonable headway reverse engineering the Java edition's PStyledText. I'll take a look at some of the open issues with .NET when I have a chance. Evan On Tuesday, 6 November 2012 17:12:18 UTC, Michael Heuer wrote: Evan Williams ev...@my-technicolour-dreams.com wrote: The C# project I'm currently working on requires functionality found in the PStyledText class currently only found in the Java implementation. As such, I plan on porting the class over. Are there any existing development efforts in this area I should know about? Alternatively, is the reason it has not been ported thus far that there is a better way of achieving the same ends in .NET? Hello Evan, Unfortunately as far as I know there aren't currently any Piccolo2D committers familiar enough with C# to help with that side of things. In fact, the Piccolo2D.NET and PocketPiccolo2D.NET codebases have been very quiet ever since the move to project hosting at Google Code. Here are a list of open issues against Piccolo2D.NET that aren't being addressed http://code.google.com/p/piccolo2d/issues/list?can=2q=Toolkit%3DPiccolo2D.NET+colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summaryx=statusy=milestonecells=tiles If you don't get any help here at piccolo2d-dev@, you may want to try piccolo2d-users@. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] draft road map
Hello Piccolo2D devs, I would like to propose the following road map for fall 2012: 1.3.1 branch: Verify issues Fixed for Milestone 1.3.2 http://code.google.com/p/piccolo2d/issues/list?can=1q=label%3AMilestone-1.3.2%20status%3AFixed Triage issues Accepted or Started for Milestone 1.3.2 http://code.google.com/p/piccolo2d/issues/list?can=2q=Milestone%3D1.3.2+colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Find a release manager for 1.3.2 release Release 1.3.2 1.3 branch: Leave at 1.4-SNAPSHOT for now 2.0 svn trunk: Resolve minimum JDK requirement for version 2.0 http://code.google.com/p/piccolo2d/issues/detail?id=190 Verify issues Fixed for Milestone 2.0 http://code.google.com/p/piccolo2d/issues/list?can=1q=label%3AMilestone-2.0+status%3AFixedcolspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Triage issues Accepted or Started for Milestone 2.0 http://code.google.com/p/piccolo2d/issues/list?can=2q=Milestone%3D2.0+colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Triage issues in New status for inclusion in a version 2.0 beta http://code.google.com/p/piccolo2d/issues/list?can=2q=status%3ANew+Toolkit%3DPiccolo2D.Java+colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summarycells=tiles Find a release manager for 2.0-beta release Release 2.0-beta 3.0 Create a new branch branches/3.0-spike and mirror on github Set minimum JDK version to 1.6 or 1.7 Refactor jdk16 and jdk16-examples back to core and examples respectively 4.0 Create a new branch branches/4.0-spike and mirror on github Refactor core APIs to have no dependencies on java.awt.* or javax.swing.* Refactor core implementation classes into at least two new modules (one Java2D plus POffscreenCanvas, one Java2D plus Swing (current PCanvas event support)) Spike on refactoring SWT, adding new Processing, Android modules I'm willing to get started on 3.0 and 4.0 soon and will proceed unless I hear otherwise. Once the branches in SVN are created, committers please feel free to jump in. For contributors who are not (yet) committers, it would be very helpful to have a read/write github mirror for those branches. I might need some help setting that up, please contact me offlist if you can help. Thanks, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Making Piccolo2D play well with Graphics2D and Java events
Jeffrey Guenther wrote: I work on a research project called CZSaw. It is a visual analytics tool for text analysis. We need a pan/zoom library that supports Swing components, handles Java events in a standard way, and plays well with Graphics2D. I have been digging through Piccolo's API and I have been noticing what seems to be a lot of code that duplicates stuff provided by Graphics2D. Ie. graphics contexts? Lines, shapes, etc? Also, as best as I can tell Piccolo implements its own event system that does not play well with Swing events. Would the developers be able to tell me the design rationale for doing things this way? Is it a legacy issue? Ie. Graphics2D and things didn't exist when it was being written. Is it technical issue? Piccolo2D implements a scene graph for zoomable user interfaces (ZUI) and is based on HCI research at UMD. Much of the design rationale for Piccolo2D is discussed in the following paper and references therein Toolkit design for interactive structured graphics http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.1.4155 http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1316870 http://ssltest.cs.umd.edu/hcil/piccolo/learn/Toolkit_Design_2004.pdf Why are PNodes not JComponents and handled by the Swing EDT? PCanvas is a JComponent. There are also non-Swing top level containers, such as POffscreenCanvas and PSWTCanvas, and a separate Piccolo2D library for Processing https://github.com/heuermh/piccolo2d-processing I really want to avoid rolling my own library and would like to modify Piccolo2D to meet our needs if possible. Sounds great, welcome. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Making Piccolo2D play well with Graphics2D and Java events
Jeffrey Guenther wrote: Thank you for the quick reply. I am familiar with the paper. Unfortunately, it does not address the event handling issues that concern me the most. What I am trying to understand is why support for Swing components through PSwing requires Swing events to be rerouted through a Piccolo event handler back into the Swing hierarchy. Why not make a PNode a JComponent, so it can be part of the Swing hierarchy? I listed three top level containers for Piccolo2D that don't use Swing. There's also an Android port that doesn't use Swing either. In the header to PSwing.java, the following is written: We are currently developing Piccolo, a scenegraph for use in 2D graphics. One of our ultimate goals is to support Swing lightweight components within Piccolo, whose graphical space supports arbitray affine transforms. The challenge in this pursuit is getting the components to respond and render properly though not actually displayed in a standard Java component hierarchy. Why wouldn't we want to put PNodes on a Java component hierarchy? It seems like the problem of supporting Swing components in the scene graph is caused by this design decision. Isn't a JComponent hierarchy already a type of scene graph? If Piccolo were to integrate into the JComponent hierarchy, we could depend on Swing to determine if nodes are picked. We could also handle the events in a more standard Java way instead of having to write event handlers that re-route the events from PNodes. Am I missing something? On Wednesday, May 9, 2012 11:56:41 AM UTC-7, Michael Heuer wrote: Jeffrey Guenther wrote: I work on a research project called CZSaw. It is a visual analytics tool for text analysis. We need a pan/zoom library that supports Swing components, handles Java events in a standard way, and plays well with Graphics2D. I have been digging through Piccolo's API and I have been noticing what seems to be a lot of code that duplicates stuff provided by Graphics2D. Ie. graphics contexts? Lines, shapes, etc? Also, as best as I can tell Piccolo implements its own event system that does not play well with Swing events. Would the developers be able to tell me the design rationale for doing things this way? Is it a legacy issue? Ie. Graphics2D and things didn't exist when it was being written. Is it technical issue? Piccolo2D implements a scene graph for zoomable user interfaces (ZUI) and is based on HCI research at UMD. Much of the design rationale for Piccolo2D is discussed in the following paper and references therein Toolkit design for interactive structured graphics http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.1.4155 http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1316870 http://ssltest.cs.umd.edu/hcil/piccolo/learn/Toolkit_Design_2004.pdf Why are PNodes not JComponents and handled by the Swing EDT? PCanvas is a JComponent. There are also non-Swing top level containers, such as POffscreenCanvas and PSWTCanvas, and a separate Piccolo2D library for Processing https://github.com/heuermh/piccolo2d-processing I really want to avoid rolling my own library and would like to modify Piccolo2D to meet our needs if possible. Sounds great, welcome. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Making Piccolo2D play well with Graphics2D and Java events
Jeffrey Guenther wrote: Sorry, I don't follow. What are you referring to with the top level containers? POffscreenCanvas renders to an offscreen BufferedImage. PSWTCanvas is a SWT component (http://www.eclipse.org/swt/). Piccolo2D for Processing library uses POffscreenCanvas to integrate with Processing (http://www.processing.org). The Android port (which may or may not be public at the moment and with which I honestly don't have much experience) probably uses an Activity (http://developer.android.com/reference/android/app/Activity.html). None of these use Swing, so it wouldn't make much sense to have PNode (or any other part of the scene graph) be a JComponent. PCanvas is a top level container that extends JComponent. PSwing is a PNode that contains a JComponent, but that JComponent is not rooted with the component hierarchy that PCanvas is contained in. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] I would like to branch the piccolo2d code base...
Ramon Santiago wrote: How would I go about doing that? I really don't want to create another googlegroups project. I plan to; update the code to use Java 6 and Java 7 features. Hello Ramon, There are already JDK6 features in the 2.0-SNAPSHOT release on the trunk http://piccolo2d.googlecode.com/svn/piccolo2d.java/trunk/jdk6 See also this issue http://code.google.com/p/piccolo2d/issues/detail?id=190 Piccolo2D development towards the 2.0 release proceeds at such a slow pace that there really isn't any need to fork or branch. Just send patches to the mailing list or better yet attach them to issues in our issue tracker. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] I would like to branch the piccolo2d code base...
Sorry, double check that link http://piccolo2d.googlecode.com/svn/piccolo2d.java/trunk/jdk16 On Thu, Mar 15, 2012 at 10:24 AM, Michael Heuer heue...@gmail.com wrote: Ramon Santiago wrote: How would I go about doing that? I really don't want to create another googlegroups project. I plan to; update the code to use Java 6 and Java 7 features. Hello Ramon, There are already JDK6 features in the 2.0-SNAPSHOT release on the trunk http://piccolo2d.googlecode.com/svn/piccolo2d.java/trunk/jdk6 See also this issue http://code.google.com/p/piccolo2d/issues/detail?id=190 Piccolo2D development towards the 2.0 release proceeds at such a slow pace that there really isn't any need to fork or branch. Just send patches to the mailing list or better yet attach them to issues in our issue tracker. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] SWT version maturity
rsksmiles wrote: Hello and happy new year to one and all. Just had a visit from a colleague who wants to include part of my piccolo2d application in an eclipse rcp based application. As eclipse rcp is swt/jface based I need to have an idea of how much work is involved in porting to swt. My experience with piccolo2d-swt has been only enough to get the examples working. The basic building blocks are there, but note that the swt package is more of a parallel implementation, not an extension. For example PSWTText extends PNode but not PText. There is an open issue with patches to SWT that unfortunately I have been slow to apply Provide advanced graphical options under SWT http://code.google.com/p/piccolo2d/issues/detail?id=189 and another SWT issue that no one has been able to look at yet PSWTText not respecting bounds.x and bounds.y in painting http://code.google.com/p/piccolo2d/issues/detail?id=219 My swing app uses a PSwingCanvas and a little bit of drag and drop. Is it a non-trivial task to migrate to the swt version? I wonder whether I can just reuse code as is in the swingcanvas and embed the swing component. Heard this is possible but not seen it done. I don't know if this would be possible. Is there a list of what is available in the different version of piccolo2d: swt and swing? Not that I know of, sorry. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Exception
Hello Beccari, It would be helpful if we could create a unit test that reproduces this error. Are you adding activities from a thread other than the AWT event thread? michael On Fri, Dec 16, 2011 at 10:31 AM, beccari.francesco beccari.france...@gmail.com wrote: Sometimes, when i run my application, I have this exception and all the activities terminate. This happens when there are many activities at the same time. Exception in thread AWT-EventQueue-0 java.lang.NullPointerException at edu.umd.cs.piccolo.activities.PActivityScheduler.getAnimating(PActivityScheduler.java: 191) at edu.umd.cs.piccolo.PCanvas.getAnimating(PCanvas.java:353) at edu.umd.cs.piccolo.PCanvas.paintComponent(PCanvas.java:589) at javax.swing.JComponent.paint(JComponent.java:1029) at javax.swing.JComponent.paintToOffscreen(JComponent.java:5124) at javax.swing.RepaintManager $PaintManager.paintDoubleBuffered(RepaintManager.java:1479) at javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java: 1410) at javax.swing.RepaintManager.paint(RepaintManager.java:1224) at javax.swing.JComponent._paintImmediately(JComponent.java:5072) at javax.swing.JComponent.paintImmediately(JComponent.java:4882) at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java: 785) at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java: 713) at javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManager.java: 693) at javax.swing.SystemEventQueueUtilities $ComponentWorkRequest.run(SystemEventQueueUtilities.java:125) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:641) at java.awt.EventQueue.access$000(EventQueue.java:84) at java.awt.EventQueue$1.run(EventQueue.java:602) at java.awt.EventQueue$1.run(EventQueue.java:600) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext $1.doIntersectionPrivilege(AccessControlContext.java:87) at java.awt.EventQueue.dispatchEvent(EventQueue.java:611) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java: 269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java: 184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java: 174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java: 169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java: 161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) Exception in thread AWT-EventQueue-0 java.lang.NullPointerException at edu.umd.cs.piccolo.activities.PActivityScheduler.processActivities(PActivityScheduler.java: 175) at edu.umd.cs.piccolo.PRoot.processInputs(PRoot.java:332) at edu.umd.cs.piccolo.activities.PActivityScheduler $1.actionPerformed(PActivityScheduler.java:222) at javax.swing.Timer.fireActionPerformed(Timer.java:291) at javax.swing.Timer$DoPostEvent.run(Timer.java:221) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:641) at java.awt.EventQueue.access$000(EventQueue.java:84) at java.awt.EventQueue$1.run(EventQueue.java:602) at java.awt.EventQueue$1.run(EventQueue.java:600) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext $1.doIntersectionPrivilege(AccessControlContext.java:87) at java.awt.EventQueue.dispatchEvent(EventQueue.java:611) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java: 269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java: 184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java: 174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java: 169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java: 161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Autocad DXF File Viewer
Robert wrote: I am in the process of developing an application to view and eventually edit autocad DXF files. A first version has been posted on my web site and is available for download along with a sample dxf file. http://nofrillsjava.com/dr/?q=node/5 Any comments gratefully received. Keep up the good work. Piccolo2D is a pleasure to develop with! Cool app, thanks for the note. Let us know if you would like a link on the Piccolo2D applications page http://piccolo2d.org/applications/index.html For exporting to PDF, I assume you are using iText's PdfGraphics2D mechanism? Document document = new Document(new Rectangle(150, 150)); PdfWriter writer = PdfWriter.getInstance(document, new FileOutputStream(filename)); document.open(); PdfContentByte pdfCanvas = writer.getDirectContent(); Graphics2D g2 = pdfCanvas.createGraphics(150, 150); PCanvas pCanvas = ...; pCanvas.paint(g2); I have an outstanding todo item regarding exporting that I need to get around to soon http://code.google.com/p/piccolo2d/issues/detail?id=223 michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] remove old Milestones from the issue tracker?
Does anyone know if I can safely remove the old Milestones from the issue tracker? Milestone-1.2.1 = Milestone for last bugfix release for 1.2 (deprecated) Milestone-1.3= Milestone for last minor release (deprecated) Milestone-1.3.1 = Milestone for last bugfix release (deprecated) Milestone-1.3.2 = Milestone for next bugfix release Milestone-1.4= Milestone for next minor release Milestone-2.0= Milestone for next major release Milestone-3.0= Milestone for future major release Or perhaps they all still need to be there for reporting purposes? I wonder what other projects on Google Code do, particularly those ones that release more often then we do. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] issues for Milestone-1.3.2
Long boring meeting this afternoon, so I did a run through the issues trying to find those appropriate for an upcoming 1.3.2 release. Please comment here or on the issues themselves. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] I've ported over the trunk code to Java 6 and cleaned up some of it...
Ramon Santiago wrote: So I basically have all the demos and tests working with a snapshot of trunk. I did an Eclipse clean on it and ran Sonar against it and cleaned up almost all the warnings. How can I contribute this back? Hello Ramon, Last time around there was opposition to moving to JDK6 as the minimum JDK requirement for piccolo2d, even on svn trunk (version 2.0-SNAPSHOT). As such, there is a separate JDK6-only module on trunk that is not part of the standard build. See http://code.google.com/p/piccolo2d/issues/detail?id=190 (and related issues 152 and 153) You may submit a patch either to the mailing list (or preferably) to the issue tracker. Though I imagine if there is a lot of source cleanup/refactoring, it might be difficult to get the patch applied. Thanks in advance for your contribution, the push towards 2.0 has been stalled for quite a while and could use a kick in the pants. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Fwd: Port Piccolo2D APIs to Android
Kenneth Flynn wrote: Michael, Responses inline. BTW, this is my main email; the gmail one is just from the google code tracker. I've attached my latest test app as an apk. This requires a phone with 2.3.3/4 right now. If you can test this, try out pinch to zoom, panning, and turning your phone on it's side to see state persist across restarts. On 8/1/2011 5:33 PM, Kenneth Flynn wrote: -- Forwarded message -- From: Michael Heuerheue...@gmail.com Date: Mon, Aug 1, 2011 at 11:10 AM Subject: re: Port Piccolo2D APIs to Android To: fly...@gmail.com Cc: piccolo2d-dev@googlegroups.com Hello Kenneth, Great to see your interest in an Android port -- we met at JavaOne a few years back. I would like to help where I can. Great! I thought we probably had met at your session at JavaOne. Since we spoke then, Android has become a very important part of our portfolio--our customers are pressing to move to Android devices, and whether that's a good idea or not, it's kind of starting to feel inevitable. The good news is that as a fresh market, we have a real chance to make an impression. The problem we're really seeing is a lack of tooling, particularly in the UI space. What really surprises me is that no one has put together a scenegraph yet, particularly including even Google to at least match the JavaFX API (although no one much seems to care about that). PIccolo seems like the obvious choice, and we have a lot of experience with it. It's funny that we're a bit in keeping with some of the original funders of Jazz (we've actually used it on DARPA projects!). I can think of a bunch of structural questions right off the bat On 1.3-branch, trunk (2.0), or both? I've started with the 1.3.1 branch, as that was the most recent release. It might make more sense to work from trunk. I was mainly interested in seeing how hard it was to do this at all. The answer to that is it seems very doable. I think there is probably a deeper question here, that you're hinting at next--there are enough things that have to be done differently that the codebase is going to end up more different than even the swt one. The biggest issue is that you must not allocate ANY objects on the paint thread under Android if you want any sort of performance. See: http://www.pushing-pixels.org/2010/08/02/shifting-gears-from-desktop-to-mobile.html And Romain Guy has some tweets linked from there as well describing the issue. I think it just turns out that Dalvik does not do nearly a good a job of allocating/deallocating objects as Hotspot or others. Combine these changes with the lack of a color object, some variations on matrices, etc... and it starts to look different enough to not be compatible. Since I posted on the issue tracker, I've gotten the PFixedBounds thing to work, but to get fixed width lines, I have to add an extra step to the paint cycle of PNode, and track all the Paints used by subobjects, which tweaks how you build PNodes. The actual use of the stroke width is all buried down in native code, and you cannot just override Paint.getStrokeWidth(). For this and to save object allocations, I'm looking at putting decorators around Paint (this is about half of a Graphics2D--the concept in Android is split between a Canvas and a Paint, which is not the same as a Java Paint, but rather more like the get/setColor, get/setFontSize etc. parts of G2) and Path (GeneralPath direct equivalent) that forward update calls back to the PNode that created them. This ends up sort of looking like PBounds but with hooks back to the object. You can see what I mean here: https://www.darkcornersoftware.com/hg/open/piccolo2d/file/64dc4e493174/piccolo2d-android-core/src/main/java/com/darkcorner/piccolo2d/ForwardingPaint.java and the fullPaint() method here: https://www.darkcornersoftware.com/hg/open/piccolo2d/file/64dc4e493174/piccolo2d-android-core/src/main/java/com/darkcorner/piccolo2d/PNode.java Of course, in my actual code production Java SE code, I don't ever use PFixedWidthStroke, but rather do the invert the transform thing to get the whole object back up to size when rendering links between nodes (which I also had to cut off on the viewport for performance, which is something we could talk about going upstream with)... But that's off topic. There are enough 'things' like this that the codebase is going to end up having some large *internal* structural differences. End users will likely be able to port their code with a minimum of changes--it's just the bits that make it go under the hood that will be different. So I think it's less an issue which version of the existing Piccolo I base this off of. Given that, I should probably be doing trunk... Will this build as a module in the current maven build, Yes. Well, probably at least two modules: piccolo-android and piccolo-android-examples. I'm building with Maven right now, and
[piccolo2d-dev] re: Port Piccolo2D APIs to Android
Hello Kenneth, Great to see your interest in an Android port -- we met at JavaOne a few years back. I would like to help where I can. I can think of a bunch of structural questions right off the bat On 1.3-branch, trunk (2.0), or both? Will this build as a module in the current maven build, or does it need to be its own project? What should the maven module and package name be? and on how we might proceed Do you want to send patches and have a developer commit them? Or commit to a git mirror and have a developer apply pull requests back to subversion? Or would you like developer access to the Piccolo2D project? My motivation is to have Piccolo2D on Android work with Processing on Android. That may complicate things a bit. http://processing.org http://wiki.processing.org/w/Android https://github.com/heuermh/piccolo2d-processing There are also some things I like about the Android APIs that might be nice to back-port functionality-wise to Piccolo2D.java proper, e.g. the animation package. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: GwtPiccolo port
I agree. I have been looking for something with features similar to http://cytoscapeweb.cytoscape.org that doesn't have the dependency on a flash library. michael On Tue, May 17, 2011 at 9:28 AM, atdixon atdi...@gmail.com wrote: Sounds like a cool project. I've done a bit with GWT and I'm looking forward to seeing it, Mia. On May 17, 2:48 am, Banang maria.patrick...@gmail.com wrote: Thanks for your reply, Michael, I appreciate it. I suspected it would be something like this (it makes perfect sense), so I'll follow your advise and host the project on Google Code for now. Mia On May 16, 5:51 pm, Michael Heuer heue...@gmail.com wrote: Banang wrote: My company has recently started a project where we hope to use Piccolo to show and manipulate graphs through a web interface. Our systems are built using GWT, which meant that the JavaScript implementation of Piccolo was of great interest to us. Last week I built a small port for parts of this implementation to GWT, which basically enables the user to implement all the examples on this pagehttp://www.machete.ca/piccolo2d.js/examples/index.htmlusing GWT. The implementation is still very sparse, and does not cover the entirety of the JavaScript implementation. My company is interested in open sourcing what we now have in the hopes that other people might benefit from (and contribute to) it as well. Therefore, I thought I'd ask what I need to do in order to get the code into your repository. I've read the hacker's guide, but since the project is already quite large (around 40 classes over 8 packages), copy-pasting it here is really not an option. I am sorry if this is a face-palm-easy-and-obvious question, I have no experience with open source projects yet so I have yet to learn the ropes. If I've posted this to the completely wrong place, or in the completely wrong form, please let me know and I'll fix it. Thanks It typically takes some time to gain commit access to an existing open source project, we're not huge on process but that is the case here as well. It might be best to host the code in some external repository for now, on say Gitorious or SourceForge or Google Code. Then you might submit a pull request or patch back to this project. Just make sure the license of your project meets the conditions of the Piccolo2D license. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] GwtPiccolo port
Banang wrote: My company has recently started a project where we hope to use Piccolo to show and manipulate graphs through a web interface. Our systems are built using GWT, which meant that the JavaScript implementation of Piccolo was of great interest to us. Last week I built a small port for parts of this implementation to GWT, which basically enables the user to implement all the examples on this page http://www.machete.ca/piccolo2d.js/examples/index.html using GWT. The implementation is still very sparse, and does not cover the entirety of the JavaScript implementation. My company is interested in open sourcing what we now have in the hopes that other people might benefit from (and contribute to) it as well. Therefore, I thought I'd ask what I need to do in order to get the code into your repository. I've read the hacker's guide, but since the project is already quite large (around 40 classes over 8 packages), copy-pasting it here is really not an option. I am sorry if this is a face-palm-easy-and-obvious question, I have no experience with open source projects yet so I have yet to learn the ropes. If I've posted this to the completely wrong place, or in the completely wrong form, please let me know and I'll fix it. Thanks It typically takes some time to gain commit access to an existing open source project, we're not huge on process but that is the case here as well. It might be best to host the code in some external repository for now, on say Gitorious or SourceForge or Google Code. Then you might submit a pull request or patch back to this project. Just make sure the license of your project meets the conditions of the Piccolo2D license. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] [VOTE] Release Piccolo2D.Java 1.3.1
Aaron Dixon wrote: This is a vote for releasing Piccolo2D.Java 1.3.1 based on release candidate 1 (1.3.1-rc1). 1.3.1-rc1 is available from the downloads page: http://code.google.com/p/piccolo2d/downloads/list?can=2q=1.3.1-rc1 This release candidate is also available from the Maven Central Repository using version 1.3.1-rc1. For example, to specify piccolo2d-core from this release candidate in your POM, use: dependency groupIdorg.piccolo2d/groupId artifactIdpiccolo2d-core/artifactId version1.3.1-rc1/version /dependency --- [X] +1 I support this release michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Are we publishing the maven site + reports?
Good question. We were as part of continuous integration builds some time back. I'm not sure those are still running. michael On Mar 20, 2011, at 3:49 PM, atdixon atdi...@gmail.com wrote: Or do we intend to? Just curious... -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: Issue 173 in piccolo2d: Slow repaint of PSwing components when zooming (from 1.2 to 1.3)
Sam Reid re...@colorado.edu wrote: I don't recall all the issues regarding direct vs buffered: were there problems knowing when the buffered image should be repainted, or do we have the same problem when it comes to direct rendering? Here's the ticket about the fuzziness problem (perhaps this is what you called fidelity?): http://code.google.com/p/piccolo2d/issues/detail?id=83 I saw this thread, but I'm not sure any of it is directly related to the question at hand: http://www.mail-archive.com/piccolo2d-dev@googlegroups.com/msg00200.html My recommendation is to make direct the default. What about using a Piccolo container to perform the buffering instead of making it a PSwing specific feature, something like: addChild(new PNodeCache(new PSwing(mySwingComponent))); There is a PNodeCache in extras already, would that class work for this use case? michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] help with issue 206
Hello devs, I'm looking for help with this issue http://code.google.com/p/piccolo2d/issues/detail?id=206 The submitted test failed on svn trunk and passes after I applied the patch there. I don't see the test fail on the 1.3 release branch, should I still apply the patch there? Thanks, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] issue triage for 1.3.1 release
Looking forward to a 1.3.1 release, the following issues have been assigned to Milestone-1.3.1 and are still open http://code.google.com/p/piccolo2d/issues/detail?id=154 http://code.google.com/p/piccolo2d/issues/detail?id=173 http://code.google.com/p/piccolo2d/issues/detail?id=181 http://code.google.com/p/piccolo2d/issues/detail?id=191 These haven't been assigned to Milestone-1.3.1 but probably should be http://code.google.com/p/piccolo2d/issues/detail?id=197 http://code.google.com/p/piccolo2d/issues/detail?id=205 This one needs further investigation or feedback from the submitter http://code.google.com/p/piccolo2d/issues/detail?id=205 michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: issue triage for 1.3.1 release
Sorry that last one should be This one needs further investigation or feedback from the submitter http://code.google.com/p/piccolo2d/issues/detail?id=174 On Fri, Feb 25, 2011 at 4:38 PM, Michael Heuer heue...@gmail.com wrote: Looking forward to a 1.3.1 release, the following issues have been assigned to Milestone-1.3.1 and are still open http://code.google.com/p/piccolo2d/issues/detail?id=154 http://code.google.com/p/piccolo2d/issues/detail?id=173 http://code.google.com/p/piccolo2d/issues/detail?id=181 http://code.google.com/p/piccolo2d/issues/detail?id=191 These haven't been assigned to Milestone-1.3.1 but probably should be http://code.google.com/p/piccolo2d/issues/detail?id=197 http://code.google.com/p/piccolo2d/issues/detail?id=205 This one needs further investigation or feedback from the submitter http://code.google.com/p/piccolo2d/issues/detail?id=205 michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Bug found in the XYArray class
jpb-phet wrote:
I believe I have found a bug in the XYArray class when I was using it
to create a PLine. Here is a simple main routine that duplicates the
bug. In the version of Piccolo that I'm using, this throws an
exception, and I've looked at the trunk and believe that the bug is
still there.
public class PiccoloBugDemo {
public static void main( String[] args ) {
XYArray pointArray = new XYArray( 10 );
pointArray.setX( 0, 5 );
System.out.println(Point count is: +
pointArray.getPointCount());
System.out.println(X value of first point in array is: +
pointArray.getX( 0 ));
}
}
The exception is thrown on the line pointArray.setX because the
number of points is incorrectly set when using this constructor.
Thanks for the note, might you be able to create an issue for this?
http://code.google.com/p/piccolo2d/issues/list
I was able to work around this easily by using a PPath and creating a
shape, which makes me wonder if it makes sense to maintain the PLIne
class and the related classes (such as this XYArray class). Perhaps
they should be deprecated.
It might make sense to keep PLine around if it is more efficient than
PPath for lines. I can't say that it is.
michael
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] how to import piccolo2d.java under eclipse
Michael Heuer wrote: To import Piccolo2D.Java into Eclipse, you'll need http://m2eclipse.sonatype.org and http://subclipse.tigris.org Then you select piccolo2d.java/trunk in the SVN repository browser and right-click Check out as Maven project... However, currently the latest version 0.12 of m2eclipse doesn't work with subclipse, see https://issues.sonatype.org/browse/MNGECLIPSE-2593 This issue is now closed and version 0.12 of the plugin is installable via the m2e-extras update site: http://m2eclipse.sonatype.org/sites/m2e-extras/ michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] problem building branches\release-1.3\swt on win 7 64bit
Carlo Salinari wrote: Being maven-ignorant (I'll study it. Promise.) I need a little hand building branches\release-1.3\swt under windows 7 64bit. My mvn -version says: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_23 Java home: C:\Program Files\Java\jdk1.6.0_23\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7 version: 6.1 arch: amd64 Family: windows following http://code.google.com/p/piccolo2d/wiki/BuildSWTOnMacOSX I tried adding this to release-1.3\swt\pom.xml: profile idwindows_64/id activation os familywindows/family archamd64/arch /os /activation properties swt.groupIdorg.eclipse.swt.win32.win32/swt.groupId swt.artifactIdx86_64/swt.artifactId /properties /profile profile but it didn't make the trick. I guess I also have to tell maven where to fetch swt.win32.win32.x86_64, right? Should I modify the parent pom? I don't believe this should be necessary. The mess with Mac OSX is because there are carbon and cocoa and ppc and intel versions of SWT and maven profiles can't properly distinguish between them. Our issue http://code.google.com/p/piccolo2d/issues/detail?id=151 links to Maven and Eclipse issues. Try these and post here $ mvn enforcer:display-info $ mvn help:active-profiles Btw: why is the dependency version[3.3.0-v3346,)/version so strict? Eclipse artifacts currently don't play nice with the Maven world, and 3.3.0-v3346 is the latest version in the Maven central repository. Most SWT users would want to build against a more recent version, which can be installed manually using something like $ mvn install:install-file -Dfile=./swt.jar \ -DgroupId=org.eclipse.swt.XXX\ -DartifactId=macosx \ -Dversion=XXX \ -Dpackaging=jar michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: problem building branches\release-1.3\swt on win 7 64bit
atdixon atdi...@gmail.com wrote:
I don't have an immediate 64-bit Windows install to try this out, but
I have a few notes for you.
The fastest route to get you up running is to install a 32-bit JDK
on your machine, point your path to that, and then run the piccolo2d
build (w/o any modifications) and that should work.
Otherwise...
* I'm not sure why Piccolo is pegged to 3.3.0 of SWT, but looking at
the older releases download section on http://www.eclipse.org/swt/,
I don't see a 64-bit version of SWT 3.3.0, there may not be one. This
is why I suggest your fastest route is to just use the 32-bit
environment.
We're pegged to that version since there are not more recent versions
in the Maven central repository. If we want to be mirrored in the
Maven central repository (which we are) then all of our dependencies
must come from there.
* If you want to try 64-bit then the SWT site *does* have 64-bit
binaries of its latest stable release (SWT 3.6.1). You should get this
64-bit version into your local maven repository and try to build
against that. It's possible/likely that SWT3.6.1 is not yet in a maven
public repo, so to get it into your local Maven repo, you'll want to
download it straight from the SWT website and then do a mvn
install:install-file to get it into your local repo. (For more on mvn
install:install-file,
http://maven.apache.org/plugins/maven-install-plugin/usage.html).
* Once you get SWT 64-bit into your local repo, then you'll need to
update the Piccolo2D swt pom to point to that. Not the parent pom, but
the *swt* pom. You'll see a dependency there that looks like this:
dependency
groupId${swt.groupId}/groupId
artifactId${swt.artifactId}/artifactId
version[3.3.0-v3346,)/version
scopecompile/scope
/dependency
You can update this directly, replacing the two ${swt.*}s with the
groupId and artifactId you specified when you did the mvn
install:install-file. Then you should be able to build, assuming
Piccolo2D works nicely on SWT 3.6.1. (You don't really need to mess
with the profiles just yet, they are a way to set swt.groupId and
swt.artifactId based on your system.)
ok, I see now that there are not separate 32-bit and 64-bit profiles
for windows. The swt pom.xml should contain two profiles
profile
idwindows/id
activation
os
familywindows/family
archx86/arch
/os
/activation
properties
swt.groupIdorg.eclipse.swt.win32.win32/swt.groupId
swt.artifactIdx86/swt.artifactId
/properties
/profile
profile
idwindows/id
activation
os
familywindows/family
archx86_64/arch
/os
/activation
properties
swt.groupIdorg.eclipse.swt.win32.win32/swt.groupId
swt.artifactIdx86_64/swt.artifactId
/properties
/profile
And depending on how arch is reported to maven, we might also need
profile
idwindows/id
activation
os
familywindows/family
archamd64/arch
/os
/activation
properties
swt.groupIdorg.eclipse.swt.win32.win32/swt.groupId
swt.artifactIdx86_64/swt.artifactId
/properties
/profile
Then download a 64-bit SWT binary and extract its swt.jar artifact.
http://download.eclipse.org/eclipse/downloads/drops/R-3.6.1-201009090800/download.php?dropFile=swt-3.6.1-win32-win32-x86_64.zip
Use
$ mvn install:install-file -Dfile=./swt.jar \
-DgroupId=org.eclipse.swt.win32.win32\
-DartifactId=x86_64 \
-Dversion=3.6.1 \
-Dpackaging=jar
to install to your local Maven repository. Then run your build.
Will create an issue for this shortly.
snip
michael
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: problem building branches\release-1.3\swt on win 7 64bit
Aaron Dixon atdi...@gmail.com wrote: Ah, thanks Michael... Do you know if the public repos have a 64-bit SWT that p2d can refer to? Not currently, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=283745 snip michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] problem building branches\release-1.3\swt on win 7 64bit
Aaron Dixon atdi...@gmail.com wrote: Carlo -- You're getting that error because you're resolving SWT 32-bit binaries but using a 64-bit JDK. (See http://stackoverflow.com/questions/2921193/swt-on-windows-64-bit) You need to: 1) Download and point your JAVA_HOME and PATH to a *32-bit* JDK before running the build. OR 2) Download the 64-bit SWT binaries and set them up in your repo AND modify the Piccolo2D swt POM to point to these. I created and fixed Issue 203, which adds the missing profiles http://code.google.com/p/piccolo2d/issues/detail?id=203 If you update from svn and follow the steps there, it should work with a 64-bit JDK. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] problem building branches\release-1.3\swt on win 7 64bit
Michael Heuer heue...@gmail.com wrote: Aaron Dixon atdi...@gmail.com wrote: Carlo -- You're getting that error because you're resolving SWT 32-bit binaries but using a 64-bit JDK. (See http://stackoverflow.com/questions/2921193/swt-on-windows-64-bit) You need to: 1) Download and point your JAVA_HOME and PATH to a *32-bit* JDK before running the build. OR 2) Download the 64-bit SWT binaries and set them up in your repo AND modify the Piccolo2D swt POM to point to these. I created and fixed Issue 203, which adds the missing profiles http://code.google.com/p/piccolo2d/issues/detail?id=203 If you update from svn and follow the steps there, it should work with a 64-bit JDK. Sorry, missed a _64 in the last commit, please update to r1100 or r1101. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] how to import piccolo2d.java under eclipse
Carlo Salinari wrote: Hi all, I'm new here. Welcome. What is the best way to import piccolo2d.java as an eclipse project? Do I have to install a maven plugin? Can you give me some hints? Do you want to work on Piccolo2D.Java itself, or just use piccolo2d in your java project? To import Piccolo2D.Java into Eclipse, you'll need http://m2eclipse.sonatype.org and http://subclipse.tigris.org Then you select piccolo2d.java/trunk in the SVN repository browser and right-click Check out as Maven project... However, currently the latest version 0.12 of m2eclipse doesn't work with subclipse, see https://issues.sonatype.org/browse/MNGECLIPSE-2593 If you just need to include Piccolo2D.Java into your project, use dependency groupIdorg.piccolo2d/groupId artifactIdpiccolo2d-core/artifactId version1.3/version /dependency in your pom.xml (similar for piccolo2d-extras and piccolo2d-swt if you need those modules). michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] how to import piccolo2d.java under eclipse
Carlo Salinari wrote: On 12/21/2010 10:19 PM, Michael Heuer wrote: Carlo Salinari wrote: Hi all, I'm new here. Welcome. Thanks. What is the best way to import piccolo2d.java as an eclipse project? Do I have to install a maven plugin? Can you give me some hints? Do you want to work on Piccolo2D.Java itself, or just use piccolo2d in your java project? I'd like to familiarize with the codebase and assess the status of the SWT port. Btw: is there anyone working (or planning to work) on it? There are outstanding issues related to SWT that I will work on from time to time, but I don't personally use SWT, so I'm less motivated to fix those. To import Piccolo2D.Java into Eclipse, you'll need http://m2eclipse.sonatype.org and http://subclipse.tigris.org Then you select piccolo2d.java/trunk in the SVN repository browser and right-click Check out as Maven project... However, currently the latest version 0.12 of m2eclipse doesn't work with subclipse, see https://issues.sonatype.org/browse/MNGECLIPSE-2593 That was really helpful. I've checked out the whole piccolo2d.java repository manually. Then I imported release-1.3 (I guess the latest stable release is the best starting point, right?) We are preparing for 1.3.1 on branches/release-1.3 (marked as 1.4-SNAPSHOT) and for 2.0 on trunk (marked as 2.0-SNAPSHOT). The big change between 1.3 and 2.0 is a package rename. Now I have 7 projects in my workspace: piccolo2d-complete piccolo2d-parent piccolo2d-core piccolo2d-examples piccolo2d-extras piccolo2d-swt piccolo2d-swt-examples (oddly enough, they are all marked as changed by the scm, except for piccolo2d-core; whatever...) What's piccolo2d-parent? Maven-related? Yep. It is the top-level pom.xml that the module poms inherit from. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] how to import piccolo2d.java under eclipse
Carlo Salinari carlo.salin...@gmail.com wrote: On 12/22/2010 12:02 AM, Michael Heuer wrote: [...] We are preparing for 1.3.1 on branches/release-1.3 (marked as 1.4-SNAPSHOT) and for 2.0 on trunk (marked as 2.0-SNAPSHOT). so you are saying I can skip 1.3 and concentrate on 2.0 directly? Depends on what you want to get out of it. 1.3.1 must retain binary compatibility with 1.3, so only minor changes are allowable there. A release for 2.0 will probably be a long ways off, since there are many unresolved issues. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] issue triage, 1.3.1 release
Hello, Thought it might be a good time to triage the open issues and begin preparations for the 1.3.1 release. There are currently only three open issues assigned to the 1.3.1 milestone http://code.google.com/p/piccolo2d/issues/detail?id=185 http://code.google.com/p/piccolo2d/issues/detail?id=188 http://code.google.com/p/piccolo2d/issues/detail?id=189 Of the new and accepted issues, these need to be assigned to a milestone http://code.google.com/p/piccolo2d/issues/detail?id=154 http://code.google.com/p/piccolo2d/issues/detail?id=157 http://code.google.com/p/piccolo2d/issues/detail?id=173 http://code.google.com/p/piccolo2d/issues/detail?id=174 http://code.google.com/p/piccolo2d/issues/detail?id=181 http://code.google.com/p/piccolo2d/issues/detail?id=191 We would then need a volunteer for release manager. I need to update http://code.google.com/p/piccolo2d/wiki/ReleaseChecklist with the Sonatype Nexus Maven repositority sync details from the 1.3. release. Is there anything else that needs to be done? michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] [RESULT] welcome Aaron Dixon as committer
I would like to welcome Aaron Dixon to the Piccolo2D project as a committer. He has been active on the piccolo2d-user mailing list and has written some nice examples in his github repository at http://github.com/atdixon/piccolo2d-examples +1 votes: Michael Heuer Chris Malley Sam Reid -1 votes: none michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] venn diagrams
Hello devs, Just wanted to let you know what I've been goofing around with lately Project web site http://www.dishevelled.org/venn-cytoscape-plugin Screencast http://www.youtube.com/watch?v=UtoW0nVwOV4 It takes advantage of the new PArea and PPath classes in the jdk16 module of svn trunk. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] [VOTE] add Aaron Dixon as committer
I would like to invite Aaron Dixon to join the Piccolo2D project as a committer. He is already listed in the parent/pom.xml as a contributor. He has been active on the piccolo2d-user mailing list and has written some nice examples in his github repository at http://github.com/atdixon/piccolo2d-examples Though I'm not sure a formal vote is neccessary, here is my +1. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] [piccolo2d] r1067 committed - JS: Adding moveToFront and moveToBack to PNode
Shoot, you don't like the new method names suggested in Issue 166? ;)
michael
On Wed, Sep 1, 2010 at 2:46 PM, piccol...@googlecode.com wrote:
Revision: 1067
Author: allain.lalonde
Date: Wed Sep 1 12:45:28 2010
Log: JS: Adding moveToFront and moveToBack to PNode
http://code.google.com/p/piccolo2d/source/detail?r=1067
Modified:
/piccolo2d.js/trunk/piccolo2d.js
/piccolo2d.js/trunk/test.html
===
--- /piccolo2d.js/trunk/piccolo2d.js Wed Sep 1 12:01:18 2010
+++ /piccolo2d.js/trunk/piccolo2d.js Wed Sep 1 12:45:28 2010
@@ -509,6 +509,32 @@
getScale: function() {
return this.transform.getScale();
+ },
+
+ moveToFront: function() {
+ if (this.parent this.parent.children.length 1) {
+ this.parent.children = this.parent.children.remove(this);
+ this.parent.children.push(this);
+
+ this.invalidatePaint();
+ }
+ return this;
+ },
+
+ moveToBack: function() {
+ if (this.parent this.parent.children.length 1) {
+ var newSiblings = [this];
+ for (var i=0, n = this.parent.children.length; in; i++) {
+ if (this.parent.children[i] != this) {
+ newSiblings.push(this.parent.children[i]);
+ }
+ }
+
+ this.parent.children = newSiblings;
+
+ this.invalidatePaint();
+ }
+ return this;
}
});
@@ -743,10 +769,10 @@
function dispatchEvent(type, event, pickedNodes) {
var currentNode, listener;
- for (var nodeIndex = 0; nodeIndex pickedNodes.length;
nodeIndex += 1) {
+ for (var nodeIndex = 0, pickedNodeCount =
pickedNodes.length; nodeIndex pickedNodeCount; nodeIndex += 1) {
currentNode = pickedNodes[nodeIndex];
while (currentNode) {
- for (var i = 0; i currentNode.listeners.length; i
+= 1) {
+ for (var i = 0, listenerCount =
currentNode.listeners.length; i listenerCount; i += 1) {
listener = currentNode.listeners[i];
if (listener[type]) {
listener[type]({
===
--- /piccolo2d.js/trunk/test.html Wed Sep 1 12:01:18 2010
+++ /piccolo2d.js/trunk/test.html Wed Sep 1 12:45:28 2010
@@ -465,6 +465,36 @@
testNode.getFullBounds();
ok(layoutChildrenCalled, layoutChildren was not called);
});
+
+ test(Move to front places child node at end of its parent's
children, function() {
+ var a = new PNode();
+ var b = new PNode();
+ var parent = new PNode();
+ parent.addChild(a);
+ parent.addChild(b);
+ a.moveToFront();
+ same(parent.children[1], a);
+ });
+
+ test(Move to back places child node at front of its parent's
children, function() {
+ var a = new PNode();
+ var b = new PNode();
+ var parent = new PNode();
+ parent.addChild(a);
+ parent.addChild(b);
+ b.moveToBack();
+ same(parent.children[0], b);
+ });
+
+ test(Move to front does nothing if child has no parent,
function() {
+ var a = new PNode();
+ a.moveToFront();
+ });
+
+ test(Move to back does nothing if child has no parent, function()
{
+ var a = new PNode();
+ a.moveToBack();
+ });
}
function testPRoot() {
--
Piccolo2D Developers Group:
http://groups.google.com/group/piccolo2d-dev?hl=en
--
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
Re: [piccolo2d-dev] Re: changes to PPath, add PShape and PArea
cmal...@pixelzoom.com cmal...@pixelzoom.com wrote: PhET's customers are the educational market, which typically lags behind the technology curve. We only recently changed our minimum system requirement to include Java 1.5. So I suspect that it will be a long time (possibly years) before we change that requirement to Java 1.6, and only once we're confident that 5% of our users are using something earlier than Java 1.6. So requiring Java 1.6 for Piccolo 2.0 would mean that we would be unlikely to upgrade any time soon. Do you have those numbers for your current users? As far as I know Mac OSX on PowerPC is the only platform that doesn't have a 1.6 JDK available. That probably is a large percentage of the educational market though. I also understand that Piccolo 2.0 will contain breaking changes. Since we have many products that use Piccolo, breaking changes will also slow our upgrade. That said... If you think it's the right thing to do, then I think you should go for it, and require Java 1.6 for Piccolo 2.0. But we aware that PhET is unlikely to be an early adopter of Piccolo 2.0. And convincing PhET management that we should be involved in 2.0 development or testing may be a tough sell. I forsee the 1.3 branch having a long lifetime, since in addition to the package name change, there will be several breaking changes in 2.0. We just need to make sure that non-breaking changes on 2.0/trunk are also merged back into the 1.3 branch. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] changes to PPath, add PShape and PArea
Thought I would ping the dev list -- I'm still looking for comments to the changes for issues Refactor PPath to use Path2D on JDK 1.6+ http://code.google.com/p/piccolo2d/issues/detail?id=152 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 A few things to consider: the changes are not binary compatible with 1.3, so they need to go in 2.0; the minimum JDK version for 2.0 would be bumped to JDK 1.6; and the current version of PPath is a widely used class. If there are no objections in a week or so, I'll add the static factory methods, complete the javadoc and unit tests, and commit to trunk. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] onward to version 2.0
Hello devs, Thank you for all your patience as we made our way through the 1.3 process. Good news is that I think we're finally done! There are plenty of issues for 2.0 to be worked on, so feel free to hack away! Cheers, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en To unsubscribe, reply using remove me as the subject.
[piccolo2d-dev] [ANNOUNCE] Piccolo2D.Java version 1.3 released
Piccolo2D.Java version 1.3 has been released. Binary and source distributions are available from the downloads page: http://code.google.com/p/piccolo2d/downloads/list?can=2q=1.3 A readme and release notes are available on the wiki: http://code.google.com/p/piccolo2d/wiki/Readme http://code.google.com/p/piccolo2d/wiki/ReleaseNotes The Piccolo2D web site, including javadoc API documentation, will be updated shortly. The Piccolo2D artifacts should be synced to the Maven central repository in a week or so. On behalf of the Piccolo2D developers, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] [RESULT] Release Piccolo2D.Java 1.3
The following people voted on release 1.3-rc4: Michael Heuer +1 Allain Lalonde +1 Marcus Rohrmoser +1 Chris Malley -0 The vote passes, and the final 1.3 release will be made soon. Unresolved issue 163 will have to be moved to a later version. On behalf of the Piccolo2D developers, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: Release Piccolo2D.Java 1.3
Chris wrote: This release is generally solid, with the exception of the pswing package. Since issue 163 has been reopened, and since I've investigated further, I think that pswing has some new problems that weren't in 1.2 (issue 163 being an example). I can't +1 the release, since my client (PhET) relies heavily on pswing. But I can't -1 the release because I think that fixing pswing and bringing it up to the same standards as the reset of Piccolo2D is going to take considerable time, and I hate to see 1.3 delayed any longer. If issue 163 were fixed, would that change your vote to +1? I wouldn't mind waiting 1.3 until that were the case. If anyone else feels strongly about pswing, then my lack of confidence in its current state may influence your vote. Otherwise, I think PhET should take the lead in fixing improving whatever version of pswing ships with 1.3. PhET uses it heavily, in some complex situations, and contributed it in (more or less) its current state. I would prefer to see PhET using a proper Piccolo2D release rather than maintaining a private fork, let us know what it will take to make that happen. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: [VOTE] Release Piccolo2D.Java 1.3
Michael Heuer wrote: Vote will close at 12:00 GMT Friday 26 February 2010. I would like to extend to vote deadline until Monday 01 March 2010 to allow for feedback on recently fixed issues 163 and 165. The current vote would pass as it stands and the fixes for those issues would not be released until a later version. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] [VOTE] Release Piccolo2D.Java 1.3
This is a vote for releasing Piccolo2D.Java 1.3 based on release candidate 3 (version 1.3-rc3). Since release candidate 2 the fix for issue 155 was rolled back and a new issue 161 has been fixed and verified. 1.3-rc3 is available from the downloads page: http://code.google.com/p/piccolo2d/downloads/list?can=2q=1.3-rc3 --- [ ] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... Votes from Piccolo2D project committers are binding, however votes from other contributors and users are welcomed. The vote must receive at least three +1 binding votes and no -1 binding votes. Vote will close at 12:00 GMT Friday 26 February 2010. On behalf of the Piccolo2D developers, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: [VOTE] Release Piccolo2D.Java 1.3
Michael Heuer wrote: This is a vote for releasing Piccolo2D.Java 1.3 based on release candidate 3 (version 1.3-rc3). Since release candidate 2 the fix for issue 155 was rolled back and a new issue 161 has been fixed and verified. 1.3-rc3 is available from the downloads page: http://code.google.com/p/piccolo2d/downloads/list?can=2q=1.3-rc3 --- [X] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: Release Piccolo2D.Java 1.3 failed
Chris wrote: All 1.3-rc1 issues that I reported have been resolved. Many thanks! What is the timeline for 1.3-rc2, and are there any other issues still pending that must be resolved? If no new issues are reported this week, I should be able to have 1.3-rc2 ready by Friday. Looking ahead to deploying the 1.3 release to the maven central repository, it would be useful if we as developers could create a KEYS file and discuss how we might be able to sign each others' keys. http://www.apache.org/dev/openpgp.html http://www.apache.org/dev/release-signing.html At a minimum, the release artifacts uploaded to maven central will need to be signed by my key, acting as release manager. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] how is source control handled for release candidates?
Chris wrote: Are release candidates created from trunk, or is there a release branch? For example... Is there a 1.3 branch, used to generate 1.3 release candidates? Or is each 1.3 release candidate generated from trunk? Since 1.3-rc1 failed, I'm trying to plan for evaluation of 1.3-rc2, and what type of testing we'll need to do. Might rc2 have new problems, or will the only changes be fixes for rc1? Do we need to do thorough testing, or just regression testing of rc1 issues? The release checklist is at http://code.google.com/p/piccolo2d/wiki/ReleaseChecklist That document is a work in progress though, since the 1.3 release will the first one handled start-to-finish by the Piccolo2D community. To answer your questions, 1.3-rc2 will be generated from trunk and svn copied to a release tag tags/release-1.3-rc2. The only differences between 1.3-rc1 and 1.3-rc2 will be fixes for Verified issues 158, 159, and 160 and some updates to the release notes. I need to leave issue 146 open in case changes need to be made to the poms for uploading to maven central. Issue 126 is still in Fixed status and should be Verified by a developer other than me. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] [VOTE] Release Piccolo2D.Java 1.3
This is a vote for releasing Piccolo2D.Java 1.3 based on release candidate 1 (version 1.3-rc1). 1.3-rc1 is available from the downloads page: http://code.google.com/p/piccolo2d/downloads/list?can=2q=1.3-rc1 --- [ ] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... Votes from Piccolo2D project committers are binding, however votes from other contributors and users are welcomed. The vote must receive at least three +1 binding votes and no -1 binding votes. Vote will close at 12:00 GMT Wednesday 27 January 2010. On behalf of the Piccolo2D developers, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: [VOTE] Release Piccolo2D.Java 1.3
Michael Heuer wrote: This is a vote for releasing Piccolo2D.Java 1.3 based on release candidate 1 (version 1.3-rc1). 1.3-rc1 is available from the downloads page: http://code.google.com/p/piccolo2d/downloads/list?can=2q=1.3-rc1 --- [X] +1 I support this release [ ] +0 [ ] -0 [ ] -1 I oppose this release because... michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Cursor remains forever after moving out from PBoundsHandle
Dominik Leszyk wrote: It seems that MOUSE_WHEEL_EVENT somehow corrupts nodes on pickPath and causes that MouseCursorUpdateHandler from PBoundsHandle doesn't pop the cursor during mouseExit method invocation. Could you give any suggestions on fixing it? Fixes were made to mouse wheel behaviour since 1.2.1, have you tried the 1.3-beta release? In the meantime, I'll see if your example can be turned into an unit test for further analysis. Thanks, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: r922 committed - Initial Piccolo2d port to Javascript....
I'm thinking this will be the easiest way to get Piccolo2D-like apps on phones. I might finally have to learn javascript. ;) michael On Tue, Jan 12, 2010 at 3:09 PM, Ben Bederson beder...@gmail.com wrote: Wow! That is amazing. Very cool! Do you have a specific project in mind that you are building this out for? - Ben On Jan 10, 7:31 pm, allain allain.lalo...@gmail.com wrote: As for now, no documentation exists. It is the first checkin on that branch after all :). Since there's no fancy JavaScript going on, I don't see why you couldn't invoke it directly from GWT. I haven't really considered packaging it for GWT, but now that you say it, it makes perfect sense. It has not yet been optimized at all, so if you do plan on making use of it, you may want to take that into account. Good luck, Allain On Jan 10, 7:20 pm, Ben Suter ben.su...@gmail.com wrote: Hi Allain, I'm glad someone has tackled this - it's been a few years since I used (the Java version of) Piccolo, but back then I was curious how long until it would be ported to JS. I've embedded Piccolo ZUI's in the browser as applets, but would love to go the plugin-free route. I checked out your examples. Do you have any documentation on how to get started using your library? In particular, do you think it would work well with GWT / do you think you might package it as a library for GWT? Thanks, Ben. On Jan 4, 12:16 pm, piccol...@googlecode.com wrote: Revision: 922 Author: allain.lalonde Date: Mon Jan 4 10:15:57 2010 Log: Initial Piccolo2d port to Javascript. It makes use of the canvas tag, which limits it to Chrome, Safari and Firefox for the time being, but there exist wrappers for IE (excanvas) and there's talk about supporting the HTML5 canvas tag in the next version. It currently supports the core functionality: - scene construction - activities.html - events (mouseup, mousedown, click, mousemove) I have tried (by using some John Resig code) to retain the basic feel of Piccolo2d even though JavaScript doesn't quite support object inheritance in the way most OO languages do. If you want to see it in action, take a look at http://www.machete.ca/piccolo2d.js/andbrowseto the examples.css There are still definitely some things missing so far, but I think this is a good start. http://code.google.com/p/piccolo2d/source/detail?r=922 Added: /piccolo2d.js /piccolo2d.js/branches /piccolo2d.js/tags /piccolo2d.js/trunk /piccolo2d.js/trunk/examples /piccolo2d.js/trunk/examples/activities.html /piccolo2d.js/trunk/examples/calendar.html /piccolo2d.js/trunk/examples/events.html /piccolo2d.js/trunk/examples/examples.css /piccolo2d.js/trunk/examples/hierarchy.html /piccolo2d.js/trunk/examples/sticky-nodes.html /piccolo2d.js/trunk/extends.js /piccolo2d.js/trunk/lib /piccolo2d.js/trunk/lib/javascript-1.6.js /piccolo2d.js/trunk/lib/jquery-1.3.2.min.js /piccolo2d.js/trunk/lib/qunit.css /piccolo2d.js/trunk/lib/qunit.js /piccolo2d.js/trunk/license-piccolo.txt /piccolo2d.js/trunk/piccolo2d.js /piccolo2d.js/trunk/test.html === --- /dev/null +++ /piccolo2d.js/trunk/examples/activities.html Mon Jan 4 10:15:57 2010 @@ -0,0 +1,97 @@ +!-- +Copyright (c) 2008-2009, Piccolo2D project,http://piccolo2d.org +Copyright (c) 1998-2008, University of Maryland +All rights reserved. + +Redistribution and use in source and binary forms, with or without modification, are permitted provided +that the following conditions are met: + +Redistributions of source code must retain the above copyright notice, this list of conditions +and the following disclaimer. + +Redistributions in binary form must reproduce the above copyright notice, this list of conditions +and the following disclaimer in the documentation and/or other materials provided with the +distribution. + +None of the name of the University of Maryland, the name of the Piccolo2D project, or the names of its +contributors may be used to endorse or promote products derived from this software without specific +prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED +WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A +PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR +ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT +LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
Re: [piccolo2d-dev] Hierachical Designs
Peter Mueller wrote: I looking for a library to graphically model state diagrams. Is it possible to draw diagrams like the following using Piccolo2D? http://www.sinelabore.com/Features_files/sc.jpg Yes. Critical aspects are: - links between nodes of all layers - nodes can contain text - hierarchy - links between nodes in different levels of hierarchy and parent nodes The model internal to Piccolo2D is that of a scene-graph, so you may use that directly for your hierarchy. Or if you would prefer, use an actual model of a state chart (e.g. State Chart XML (SCXML) project at Apache Commons, http://commons.apache.org/scxml/) and implement strictly the view in Piccolo2D. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Piccolo2D.Java 1.3-beta released
Hello devs, Piccolo2D.Java 1.3-beta has been committed to trunk, copied to the svn tag tags/release-1.3-beta, and made available on the Google Code downloads page. Please review these. Any showstopper issues should probably go immediately into another 1.3-beta release. Major and minor issues with 1.3-beta can be addressed in an upcoming 1.3-RC-1 release, in one or two weeks' time. I'll post an announcement to piccolo2d-users on Monday. Cheers! michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Default fonts for PText and PHTMLView
Samuel Robert Reid wrote: My team and I write piccolo applications that need to support many languages, and the default fonts specified in PText and PHTMLView often need to be replaced (or glyphs can appear as empty boxes). We are currently overriding these fonts on a case-by-case basis, but I wanted to discuss the possibility of being able to specify these globally, such as Swing does in UIManager. I think there's good reason to keep the default fonts static and final in core (PText and PHTMLView) since calling out to Swing doesn't always make sense (e.g. a client may be using POffscreenCanvas). Perhaps you could create a factory for PText and PHTMLView nodes that sets the font to the font UI resource provided by the Swing Look and Feel mechanism? Or maybe those factory methods should exist on PSwingCanvas? michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] maven 3.0 warnings
Hello,
Maven version 3.0-alpha-3 gives a slew of warnings on our build, many
of which should probably be addressed before 1.3. Let me know what
you think.
michael
$ mvn -version
Apache Maven 3.0-alpha-3 (r834122; 2009-11-09 10:04:41-0600)
$ mvn install
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.piccolo2d:piccolo2d-complete:pom:1.3-SNAPSHOT
[WARNING] The expression ${pom.artifactId} is deprecated. Please use
${project.artifactId} instead. @
org.piccolo2d:piccolo2d-complete:1.3-S
NAPSHOT, C:\cygwin\home\heuermh\working\piccolo2d.java-trunk\pom.xml
[WARNING] The expression ${pom.version} is deprecated. Please use
${project.version} instead. @
org.piccolo2d:piccolo2d-complete:1.3-SNAPSHO
T, working\piccolo2d.java-trunk\pom.xml
[WARNING] 'build.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-scm-plugin @
org.piccolo2d:piccolo2d-complete:1.3-SNA
PSHOT, working\piccolo2d.java-trunk\pom.xml
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.piccolo2d:piccolo2d-parent:pom:1.3-SNAPSHOT
[WARNING] The expression ${pom.artifactId} is deprecated. Please use
${project.artifactId} instead. @
org.piccolo2d:piccolo2d-parent:1.3-SNA
PSHOT, working\piccolo2d.java-trunk\parent\pom.xml
[WARNING] The expression ${pom.version} is deprecated. Please use
${project.version} instead. @
org.piccolo2d:piccolo2d-parent:1.3-SNAPSHOT,
working\piccolo2d.java-trunk\parent\pom.xml
[WARNING] 'build.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-scm-plugin @
org.piccolo2d:piccolo2d-parent:1.3-SNAPS
HOT, working\piccolo2d.java-trunk\parent\pom.xml
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.piccolo2d:piccolo2d-core:bundle:1.3-SNAPSHOT
[WARNING] The expression ${pom.artifactId} is deprecated. Please use
${project.artifactId} instead. @
org.piccolo2d:piccolo2d-core:1.3-SNAPS
HOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] The expression ${pom.version} is deprecated. Please use
${project.version} instead. @
org.piccolo2d:piccolo2d-core:1.3-SNAPSHOT, C
:\cygwin\home\heuermh\working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'build.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-scm-plugin @
org.piccolo2d:piccolo2d-core:1.3-SNAPSHO
T, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-checkstyle-plugin @
org.piccolo2d:piccolo2d-core:
1.3-SNAPSHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-javadoc-plugin @
org.piccolo2d:piccolo2d-core:1.3
-SNAPSHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-surefire-report-plugin @
org.piccolo2d:piccolo2d-
core:1.3-SNAPSHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-changelog-plugin @
org.piccolo2d:piccolo2d-core:1
.3-SNAPSHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-jxr-plugin @
org.piccolo2d:piccolo2d-core:1.3-SNA
PSHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.codehaus.mojo:taglist-maven-plugin @
org.piccolo2d:piccolo2d-core:1.3-SNAPSH
OT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-project-info-reports-plugin @
org.piccolo2d:picco
lo2d-core:1.3-SNAPSHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-pmd-plugin @
org.piccolo2d:piccolo2d-core:1.3-SNA
PSHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.codehaus.mojo:jdepend-maven-plugin @
org.piccolo2d:piccolo2d-core:1.3-SNAPSH
OT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.codehaus.mojo:cobertura-maven-plugin @
org.piccolo2d:piccolo2d-core:1.3-SNAP
SHOT, working\piccolo2d.java-trunk\core\pom.xml
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.piccolo2d:piccolo2d-extras:bundle:1.3-SNAPSHOT
[WARNING] The expression ${pom.artifactId} is deprecated. Please use
${project.artifactId} instead. @
org.piccolo2d:piccolo2d-extras:1.3-SNA
PSHOT, working\piccolo2d.java-trunk\extras\pom.xml
[WARNING] The expression ${pom.version} is deprecated. Please use
${project.version} instead. @
org.piccolo2d:piccolo2d-extras:1.3-SNAPSHOT,
working\piccolo2d.java-trunk\extras\pom.xml
[WARNING] 'build.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-scm-plugin @
[piccolo2d-dev] @since tags in extras, swt
I haven't been able to get clirr to run for the extras or swt modules yet $ clirr.sh --old-version ../piccolo2d.java-release-1.2.1/build/piccolox.jar --new-version extras/target/piccolo2d-extras-1.3-SNAPSHOT.jar --orig-classpath ../piccolo2d.java-release-1.2.1/build/piccolo.jar --new-classpath core/target/piccolo2d-core-1.3-SNAPSHOT.jar --style text $ clirr.sh --old-version ../piccolo2d.java-release-1.2.1/build/piccolox.jar --new-version swt/target/piccolo2d-swt-1.3-SNAPSHOT.jar --orig-classpath ../piccolo2d.java-release-1.2.1/build/piccolo.jar --new-classpath core/target/piccolo2d-core-1.3-SNAPSHOT.jar --style text ... Unable to complete checks:Unable to locate enclosing class edu.umd.cs.piccolox.event.PStyledTextEventHandler$3 for nested class edu.umd.cs.piccolox.event.PStyledTextEventHandler$3$1 so we'll have to add @since 1.3 tags manually to those modules. michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: invalidatePaint does not cause a repaint unless other events are occurring
I think this is supposed to be analogous to the AWT
Component.invalidate() method
http://java.sun.com/javase/6/docs/api/java/awt/Container.html#invalidate%28%29
A client might call invalidatePaint() a lot of times before an actual
repaint happens.
michael
Allain Lalonde wrote:
It would seem that indeed, this behavior is intended, though I can't see
why?
invalidatePaint() is used to flag nodes as needing a repaint, but the method
that is primarily responsible for making use of that flag is
validateFullPaint() which is only gets called from PRoot.processInputs().
It seems that calling repaint does the same thing, but is correctly handled
by Swing since it you follow the execution path ultimately, it ends up
callingin 'component.repaint(...);'.
Can someone shed some light on why this is the way it's written?
It would seem to me that a call to repaint() is needed at the end of
invalidatePaint() so that the need for repainting bubbles up to the
underlying Component.
2009/11/2 Allain Lalonde allain.lalo...@gmail.com
Good eye, invalidate paint just flags the node as needing to be
repainted. This gets picked up on the next ui cycle. I don't believe
that it will automatically bubble up the stack, though i will need to
re-read the code to confirm this. I will examine your code when i get
home to see if i can repelicate your issue.
Thank you for bringing this up.
On 02/11/2009, Nigel nigel.tamp...@f2s.com wrote:
The comment in PNode.java reads
// When you do create you own nodes the only method that you will
// normally need to call is invalidatePaint. This method marks the
// nodes as having invalid paint, the root node's UI cycle will
then
// later discover this damage and report it to the Java repaint
manager.
However, I find that after calling invalidatepaint() the repaint
manager does not discover the damage unless other events are occurring
(such as moving the mouse around).
I was expecting that calling invalidatePaint would result in the node
being repainted some time later - am I doing something wrong or is
Piccolo?
Here is a contrived example (ClockNode.java) - It displays 4 custom
nodes, each showing a clock's second hand. The top 2 clocks are
updated from within the event dispatch thread, the lower 2 clocks are
updated from another thread. The 2 clocks on the left are redrawn via
a call to repaint and the 2 on the right via a call to
invalidatePaint.
if you run it you'll see the clock on the right (calling
invalidatePaint) are only redrawn if you are moving your mouse over
the window.
ClockNode.java
import java.awt.*;
import java.awt.geom.*;
import edu.umd.cs.piccolo.*;
import edu.umd.cs.piccolo.util.*;
import edu.umd.cs.piccolox.PFrame;
public class ClockNode extends PNode {
private GeneralPath secondHand;
private int tseconds; // 10ths of seconds
public void tick() {
tseconds++;
if ( tseconds = 600 ) { tseconds = 0; }
// inform Piccolo that the node needs to be redrawn
if ( useRepaint ) {
repaint();
} else {
invalidatePaint();
}
}
private boolean useRepaint;
public ClockNode(boolean useRepaint) {
this.useRepaint = useRepaint;
// create the needle shape
secondHand = new GeneralPath(GeneralPath.WIND_EVEN_ODD);
secondHand.moveTo(-0.1,0);
secondHand.lineTo(0,1);
secondHand.lineTo(0.1,0);
secondHand.closePath();
}
public void paint(PPaintContext aPaintContext) {
Graphics2D g2 =
(Graphics2D)aPaintContext.getGraphics().create(); //
create - as we mess with the transform
g2.setPaint(Color.BLACK);
//draw the face
g2.draw( new Ellipse2D.Double( getX(), getY(), getWidth(),
getHeight
() ));
//draw the second hand
g2.translate(getX()+getWidth()/2,getY()+getHeight()/2); //
translate
hand so 0,0 is centre of bounds
g2.scale(getWidth()/2,getHeight()/2); // scale the needle
g2.rotate ( Math.toRadians((tseconds*6)/10f+180) );
g2.fill(secondHand);
}
public static void main(String args[]) {
// top left clock - uses repaint
final ClockNode clockNode1 = new ClockNode(true);
clockNode1.setBounds(0,0,200,200);
// top right clock - uses invalidatePaint
final ClockNode clockNode2 = new ClockNode(false);
clockNode2.setBounds(210,0,200,200);
// lower left clock - uses repaint
final ClockNode clockNode3 = new ClockNode(true);
[piccolo2d-dev] 1.3 issue triage
I've verified all the fixed issues I can from the list on the wiki page http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3 I wasn't able to verify 88/106, and added an example demonstrating the issue. michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] remove UmlGraph doclet?
Hello, Does anyone mind if we remove the UmlGraph doclet? I don't find the results particularly helpful or interesting, and there are some issues with configuration in our pom files, e.g. examples/pom.xml 41: !-- don't use UmlGraph as the current settings (see ../parent/pom.xml) cause pain with swt -- michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: PScrollPane and interactingRenderQuality
Lionel wrote: Hi every body ! I'm a piccolo fan for a few years. I have only coded a couple of projects with this framework but it really rocks. I'm glad piccolo2D is taking over ! I'm facing a little issue ... maybe a bug ? ... concerning PScrollPane and the rendering quality during interaction. If you move the canvas around by just clicking on it (regular PPanEventHandler) then the rendering quality changes as the user is interacting... the final high quality rendering is properly set when the interaction stops. This behaviour does not happen with the scroll pane when the user interacts with the scroll bars... Can anyone point me in a direction where I could solve this ? If there are some modifications to be done to piccolo itself, I can try to do it and post my work back... (if I manage to do it properly ! :o) Thanx in advance for your tips ! There is a method setInteracting(boolean) on PComponent http://www.piccolo2d.org/doc/piccolo2d.java/release-1.2.1/apidocs/edu/umd/cs/piccolo/PComponent.html#setInteracting(boolean) Somewhere in PScrollPane we need to add calls to set interacting to true on scrollbar mouse down and to set interacting to false on mouse up. Could you create a new issue at http://code.google.com/p/piccolo2d/issues/list for this? Thanks, michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .Net version: tasks for 1.3?
Mark wrote: Regarding issue 115: http://code.google.com/p/piccolo2d/issues/detail?id=115 What task are needed to for the .Net version and the Piccolo 2D 1.3 release? There were a few bugs reported for the 1.2 release, so those would need fixed. All the milestones in the issue tracker for 1.3 are for the Java version. My interest: I have a project coming up later this year in which I plan to use Piccolo.Net and I would like to see it stay current with the other versions. So I'm willing to make some time to keep it current. Most important in my mind is http://code.google.com/p/piccolo2d/issues/detail?id=60 The Piccolo2D devs can't work on the .Net version if we can't build it. None of the.Net issues have been assigned a version since we are unable to evaluate them. After that, the general tasks would be: Update the copyright/license headers Create a build process that can be automated (with NAnt, I suppose) Start creating a unit test suite (NUnit) Add build tools for calculating source code metrics, if available Evaluate issues fixed in Piccolo2D.Java since 1.2 to see if they are applicable to .Net versions Document a release process for .Net artifacts If there isn't much to fix in the .Net codebase other than the build stuff, we could release a version 1.2.1 fairly quickly. michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: [piccolo2d] r628 commited - FingBugs Hunting.
snip /piccolo2d.java/trunk/extras/src/main/java/edu/umd/cs/piccolox/pswing/PSwing.java /** * The cutoff at which the Swing component is rendered greek */ - private final double renderCutoff = 0.3; + private static final double GREEK_SCALE_CUT_OFF = 0.3d; Similar values in PText are called greekThreshold and DEFAULT_GREEK_THRESHOLD. PText also has get/setGreekThreshold. private JComponent component = null; private double minFontSize = Double.MAX_VALUE; - private Stroke defaultStroke = new BasicStroke(); + private transient Stroke defaultStroke = new BasicStroke(); private Font defaultFont = new Font(Serif, Font.PLAIN, 12); Should these defaults be static and final? Strange that PSwing overrides protected void paint(PPaintContext) with public void paint(PPaintContext). I recommend refactoring to public void paint(PPaintContext) -- protected void paint(PPaintContext) public void paintAsGreek(Graphics2D) -- protected void paintGreek(PPaintContext) public void paint(Graphics2D) -- protected void paintComponent(PPaintContext) Subclasses might want access to the entire paint context for paintGreek and paintComponent, not just the graphics. I wonder how much work this change would be though. . . michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: [piccolo2d] r628 commited - FingBugs Hunting.
Breaking binary compatibility is not really an issue with extras. I still wouldn't do it lightly though. I'm not a user of PSwing, is it a common to extend it in client code? I will create an issue and an updated patch with some additional API cleanup for review. michael allainallain.lalo...@gmail.com wrote: Yes they should be protected, should you do it? No. Not until 2.0 at least since client code that calls it directly would break. If you want to do it anyway, I'm all for it, but since we're not marking constants as final till 2.0, this one seems like a no go till then either. On Jul 30, 4:31 pm, Michael Heuer heue...@gmail.com wrote: snip /piccolo2d.java/trunk/extras/src/main/java/edu/umd/cs/piccolox/pswing/PSwin g.java /** * The cutoff at which the Swing component is rendered greek */ - private final double renderCutoff = 0.3; + private static final double GREEK_SCALE_CUT_OFF = 0.3d; Similar values in PText are called greekThreshold and DEFAULT_GREEK_THRESHOLD. PText also has get/setGreekThreshold. private JComponent component = null; private double minFontSize = Double.MAX_VALUE; - private Stroke defaultStroke = new BasicStroke(); + private transient Stroke defaultStroke = new BasicStroke(); private Font defaultFont = new Font(Serif, Font.PLAIN, 12); Should these defaults be static and final? Strange that PSwing overrides protected void paint(PPaintContext) with public void paint(PPaintContext). I recommend refactoring to public void paint(PPaintContext) -- protected void paint(PPaintContext) public void paintAsGreek(Graphics2D) -- protected void paintGreek(PPaintContext) public void paint(Graphics2D) -- protected void paintComponent(PPaintContext) Subclasses might want access to the entire paint context for paintGreek and paintComponent, not just the graphics. I wonder how much work this change would be though. . . michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: [piccolo2d] r591 commited - Starting to refactor PStyledText. It's a beast. Too bad we don't have ...
On Mon, Jul 27, 2009 at 6:10 PM, codesite-nore...@google.com wrote: Revision: 591 Author: allain.lalonde Date: Mon Jul 27 16:09:53 2009 Log: Starting to refactor PStyledText. It's a beast. Too bad we don't have any code that really puts it through its paces. http://code.google.com/p/piccolo2d/source/detail?r=591 Modified: /piccolo2d.java/trunk/extras/src/main/java/edu/umd/cs/piccolox/nodes/PStyledText.java ... Hello Allain, Might you create an issue for this? It's not obvious what your intent is -- so far it appears as if you are just cleaning up the code, right? michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: FindBugs Plugin to Maven
allainallain.lalo...@gmail.com wrote: Any objections to me adding the FindBugs Plugin to maven build? No objections here. In larger projects of mine, the maven plugin blows up with memory problems, so you may have to tweak the default JVM and FindBugs settings a bit. michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: Any objections to me adding Cobertura coverage report to the Maven Build?
allain wrote: My reasons for wanting to do this are: - Obviously Code Coverage Metrics are good but this one is IDE agnostic. - It has a Hudson plugin that can be installed allowing us to diagram the (hopefully) increasing progression of code coverage over time in a nice convenient graph. http://wiki.hudson-ci.org//display/HUDSON/Cobertura+Plugin The javascript code used in the Cobertura reports themselves are licensed under the GPL, and there was concern in e.g. the Apache Commons community that distributing those reports violates the terms of the license. You may find some discussion threads in archives of the commons-dev mailing list. I can't recall what the resolution of the issue was though. michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: OpenGL (ES?) / OpenVG / SVG / non-JDK environments
M. Rohrmoser wrote: I'm currently thinking about how to do graphics with an performant, easy-to-use and moderately platform neutral way. Maybe it's time to drop the java2d layer and target OpenGL directly? OpenGL seems to be widely available - and JOGL even is integrated with JDK 1.6. But a simple scenegraph API is highly desireable - and P2D is the simplest I've seen so far. And which is the best candidate for the underlying renderer? OpenGL? OpenGL ES? Is there such a thing as JOGL-ES? OpenVG sadly seems to be irrelevant (no implementations available). The longer I think about it, the more I'd love to see a SVG-IO enabled, OpenGL (ES) backed, /simple/ 2D scenegraph API. Or is in times of 3D-, shadow- and highlighting-effects on buttons etc. OpenGL the inevitable choice anyhow? But I don't like the idea to use blender for GUI design - I'd very much prefer a SVG editor like inkscape. What do you think about that? Is it sensible to push P2D in that direction? M P.S.: I had a brief look into some APIs but didn't see something as simple as P2D. Check out those Webstart demos: http://slick.cokeandcode.com/static.php?page=demos http://slick.cokeandcode.com/thingle/ http://www.fenggui.org/doku.php#misc http://www.lwjgl.org/demos.php http://www.jmonkeyengine.com/movies_demos.php https://jogl-demos.dev.java.net/ Let me add Processing to this list http://dev.processing.org/reference/core/ They have multiple implementations of their PGraphics API. I wrote a hack to use Piccolo2D in Processing, but it requires using the Java2D implementation of PGraphics. It would be nice to have a portable version of Piccolo2D's scenegraph. michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .net version maintenance
sprucely wrote: Has anyone looked into tools that automatically convert from Java to C#? I know not everything cleanly maps, but for the code that is equivalent it would greatly enhance the maintainability of the .Net version. One tool I'm aware of is Sharpen which is used to maintain both Java and .Net versions of db4o... http://developer.db4o.com/blogs/product_news/archive/2008/05/21/sharpen-your-java-app-now-java-to-c-converter-released-as-free-software.aspx We are admittedly short C# maintainers, so anything that may help is a bonus. From my point of view, getting Piccolo2D.Net to build with mono would be a great first step, as it would allow some of us Piccolo2D.Java developers without access to Microsoft built tools to contribute. http://code.google.com/p/piccolo2d/issues/detail?id=60 michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
