Skip to main content

Blog Archive for rbair during August 2005

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 ...er... that they need more work. One such project (affectionately named JavaApplication1) is a front end for IssueZilla....
"Not Invented Here", a clever phrase often used as a pejorative to indicate that somebody (usually due to ego?) would rather reinvent the wheel and write their own implementation than leverage an existing (and by implication, better) implementation. In this entry I try to shed some light on real technical reasons why "rolling your own" may be better than relying on somebody...
In my last blog's comments Andy Roberts asked the following question: I always keep my eye on SwingLabs because it is adding great value to the existing Swing toolkit. One thing that confuses me is just *how* it interacts with Swing, within the development process, that is. SwingX is an incubator for neat features, for example, sortable tables. Yet the approach adopted by Swing devs in Mustang...
Around June of last year I first became aquainted with the JDNC project. As a professional Swing application developer, I was very interested in an open source project that would make my job easier. It was clear to me that JDNC was positioned at the right time to make a huge impact on rich client application development. Swing is an excellent UI toolkit. It provides clean abstractions between the...