Issue 126 ; attempting to use a version range specifier, will grab 3.3.0-v3346 from maven central repo where available, or will require user to install manually where not available, e.g. macosx_cocoa_intel profile

Adding site info back to root, since it seems to behave differently in hudson than on desktop.

Moving site info into parent module so that submodules sites can be built independently.

Rolling back removal of parent module. Seems that it's needed for correct generation of correct reports navigation system. Marcus has wisely suggested that the poms for central should be hand crafted, rather than trying to shoe horn the current, working, poms into their format.

mvn site:site site:deploy for the complete project

adding Point2D getCenter() method to PSWTPath, with unit tests

Expanding new PSwing example.

rolling back changes errantly committed in r835

adding additional constructor PInterpolatingActivity(long duration)

Deleting parent module since maven repo doesn't support parent modules in the way we were using them.

Removing inclusion of parent module from complete.

Remove SWT-Examples dependency on parent module.

Remove SWT dependency on parent module.

Remove Extras dependency on parent module.

Removing Core's Dependency on parent module.

Issue 133 ; cleaning up SWT package class-level javadoc

Testcase for issue#142, followup to r816

cleaning up checkstyle warnings introduced by latest refactorings.

Fixing new PMD warnings.

Issue 126 ; adding explicit versions for macosx and win32 x86 deps, which were missing before; also adding hack for 3.5.0 dep versions, abusing an Apache SVN web interface URL as an external maven repo

issue#142 fixed IMO

see issue#142

increasing test coverage

Thanks to Nigel for pointing out: ...

I notice that the following line in TooltipExample.java

  final PNode n = event.getInputManager().getMouseOver().getPickedNode
();

Could be rewritten simply as:

final PNode n = event.getPickedNode();

As per Issue # 27, I'm making the repainting of the canvas lazier. ...

During an animation it'll record what bounds have actually been dirty, then rather than repainting the entire scene, it'll only paint the region that's been dirtied.

Adding Tests to PSwing Event Handlers

Making PSwing examples zoom to contain entire scene on startup.

Rolling Back All paint changes to PSwing. It was working acceptably for clients and the changes were breaking changes. A rollback is the simplest thing to do to get this into a "working" state again. ...

Also, starting on a cleaner PSwing Example to really test all the edge cases we can.

making PCamera internally consistent with regards to layer references, best we can do without making related methods final

adding license headers for core unit tests