Ramon, Based on what I see in the license in the distribution, you can freely modify the code as long as you provide the license disclaimer. I have run into a number of problems with Piccolo2D as well and am willing to help you in your forking effort. My research group has a number of needs that are not being met by the current code base. ZVTM is another zoomable library, but is too far off the Java standard way for me to be too interested in adapting it. Piccolo just needs a little modernizing love.
Let me know if you are interested and we'll start to figure out the details. Jeff On Thursday, March 15, 2012 9:57:40 AM UTC-7, Ramon Santiago wrote: > > I know about the stalled work that is already there for java6. > > It's no where near to maximizing the currently available language features > and APIs. > e.g. No generics? > > I have also read issue 190. The last comment pretty much sums up the > problem I'm trying to correct. > Not only was Java 5 EOL, but Java 6 will be soon. Java 7 has been out for > over a year. > > I want to branch. The branch will break backward compatibility. > People who either can not or will not use the branch, do not have to. > That's why it's a "branch". > > Is there something specif in the license that prohibits me from creating a > branch or just opening up > another google code project and proceeding from there? > > thanks > rjs > > > > > On Thursday, March 15, 2012 11:27:38 AM UTC-4, Michael Heuer wrote: >> >> 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