[VOTE] Demos and SwingLabs-Demos
The more subprojects we add to SwingLabs, the nastier SwingLabs-demos gets. For those not up to speed, the swinglabs-demos project contains both a general demo infrastructure, and specific demos for SwingLabs components.
Unfortunately, this leads to a large inter project dependency that is getting hard to maintain. Whenever a change is made to a SwingX component, for instance, we then have to open up the SwingLabs demos project and update the demo there.
As a result, we often see Josh and myself writing little main methods in the SwingX project to test the component rather than going through the hassle of updating the swinglabs-demos demos. Clearly, this isn't good.
What I propose is clearing out the specific demos from swinglabs-demos. Let swinglabs-demos contain a common demo framework (code for switching look and feels, showing documentation, etc). Let a copy of the swinglabs-demos jar be placed within each swinglabs subproject in a lib/demos directory. Then have a src/demos source directory. So it would look something like this, for all swinglabs sub projects:
<br /> SwingX<br /> - bin<br /> - dist<br /> - lib<br /> - cobundle<br /> - optional<br /> - demos<br /> - src<br /> - beaninfo<br /> - demo<br /> - java<br /> - test<br />
What do you think? I'll leave this question open until Jeanette comes back.