Issue 37 ; refactoring example packages to org.piccolo2d.examples and org.piccolo2d.extras.swt.examples for examples and swt-examples respectively

Issue 37 ; refactoring package edu.umd.cs.piccolox.swt to org.piccolo2d.extras.swt in swt

Issue 37 ; refactoring package edu.umd.cs.piccolox to org.piccolo2d.extras in extras

Issue 37 ; refactoring package edu.umd.cs.piccolo to org.piccolo2d in core

Commenting out test that doesn't work under XVnc

Adding tests to ensure PSwing plays well with FEST. ...

Proves(?) Issue #33 can be closed.

Issue 177 ; adding additional unit tests and applying patch

Issue 177 ; adding unit test for selection notification on delete key event

Issue 172 ; increasing test coverage, javadoc improvements, checkstyle fixes

Fixing Issue 172

Making PNode.print() throw PrinterException rather than swallowing it. ...

This is until we remove printing support from PNode as per Issue 102.

Making checkstyle allow missing javadocs on getters. Leaving it up to the developer to decide if a javadoc is nessary.

Adding Deep Copy Test to PNode.clone()

Removing dead class since all methods that invoked it were deprecated and so have been deleted.

Removing unnecessary local variables from validateFullBounds.

Marking accessor for PNotificationCenter Singleton as synchronized. This one was caught by poster in http://code.google.com/p/piccolo2d/issues/detail?id=136#c4

Removing Deprecated code

Fixing Issue 136. PNotificationCenter is being made final so that subclasses can't create multiple instances of it

Deleting PUtilTest since it no longer had any tests

Changing constants to final as per Issue #135

Issue 146 ; committing patch to trunk

updating version to 2.0-SNAPSHOT

updating version to 1.3

Issue 163: restore component.revalidate call in constructor to get us back to state of PSwing r965

Issue 163: Removed infinite loop introduced in r978 by calling component.revalidate in PSwing.updateBounds. With the removal of HeirarchyBoundsListener in r978, this should put PSwing back to r965, the state it was in before we started working on this issue.

Fixes issue 163. ...

- Removed the HiercharyBoundsListener that was added in r973, it was not totally effective, and it's not clear why it was partially effective.
- Added component.revalidate to updateBounds, so that bounds are computed based on correct component size.
- Removed redundant call to component.revalidate in constructor, since the constructor calls updateBounds.

updating version to 1.3rc4

Issue 166 ; improved javadoc comments for moveToFront and related. Fixes issue 166.

Fix for Issue 163 changes in size of node itself were being detected, but not changes in the size of its progeny. ...

I'm not entirely sure why a method called "ancestorResized" gets called when a subcomponent changes... but I'm not going to complain. Just works.

updating version to 1.3-rc3