Skip to main content

Every Project needs a Name

Posted by rbair on August 26, 2005 at 4:16 PM PDT

An invaluable tool for ensuring good API design is to, well, use your own APIs. I usually have a half dozen partially completed apps in my workspace which I use to test the SwingLabs components and APIs. Sometimes I find our code to be extremely helpful, and sometimes I find that they need more work.

One such project (affectionately named JavaApplication1) is a front end for IssueZilla. I was putting issues into the DataBinding project and just couldn't take it anymore. That web UI is horrible! So I wrote a quick and dirty rich client implementation.

In the process of writing this little app, I started testing some of the edges of our databinding APIs, and found places that worked really, really well and places that needed some more work. I thought this would be a very valuable project to have on for a couple of reasons:

1) Demos are only worth so much. Until we have a full application built on the SwingLabs components, we won't really know how well our stuff works

2) An application available to SwingLabs developers to collaborate on would make the process of discussing use cases and edge cases much easier

3) The world could benefit by not having to use the IssueZilla web UI (*shiver*)

Which brings me to the difficult question of the day -- what should I call it?


PS> Why yet another bug-viewer/project management/whatever tool? Because I doubt I could convince somebody else with any legitimate code base to allow us to muck with it and rewrite the whole app to use SwingLabs components

PPS> No, this project is _not_ part of SwingLabs, so you don't have to be a SwingLabs developer or sign the JCA to develop for it. And yes, we'll be reusing other open source code whereever possible