Fixed Issue # 160 ...

Removing component listener from PSwing constructor. Caused more problems than it solved.

Made PSwing.setVisible lazily call its component's setVisible method depending on its current visibility. This should stop the stack overflow being experienced by Chris Malley. Since I have been unable to reproduce it, I can't test it.

Unit Test demonstrating Issue 158

Fixing Issue 158 - With event handlers not being installed properly for nodes after they get removed and then re added to a Scene.

updating copyright years to include 2010

Unnecessary import.

Modifying SwingLayoutNode so that it accepts a Container during construction. Otherwise, creating a node that uses BoxLayout is impossible without making the node's layout mutable.

Removing setLayout method. Effectively making the layout final.

Stab 2, easy redundant public modifiers.

First attack on checkstyle.

Initial import of code for Issue #150.

adding @since 1.3 tags

I agree completely. Comments of that kind are pretty useless, but instead of just mentioning it, why not fix it? ...

I disagree with having developer names in files at all. If we didn't have subversion to track contributions it'd make sense.

I totally disagree with a commenting style ...

/**
 * Returns the width of the line.
 * 
 * @return stroke width
 */
public float getLineWidth()

I prefer to not see my name in such source files.

More checkstyles on PSwing.

CheckStyle and final fixes.

Fixing CheckStyle warnings on PScrollpane. Including tabs, finals and missing javadocs.

Fixed Issue 131

Making PSwing nodes automagically disable double buffering on all children of the underlying JComponent. ...

Also, renamed reshape() as updateBounds() and changed its visibility to public.

Applying PSwing file provided by sreid. Javadocs have been re-added. And some Refactoring has taken place.

Testcase for issue#142, followup to r816

cleaning up checkstyle warnings introduced by latest refactorings.

Fixing new PMD warnings.

issue#142 fixed IMO

see issue#142

Adding Tests to PSwing Event Handlers

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.

adding license headers for extras and swt unit tests

adding license headers for extras unit tests

Rolling back deprecation from r765. Users shouldn't need to know that PFixedWidthFont is an adapter to an underlying BasicStroke.