The Programmers Stone looks like something to read in my “copious free time”.
welcome to The Programmers’ Stone. The purpose of this site is to recapture, explore and celebrate the Art of Computer Programming. By so doing we hope to help the reader either become a better programmer, understand what less experienced programmers are struggling with, or communicate more effectively with other experienced programmers.
Many topics are covered, so this will require a bit of reading before I can even formulate an opinion on its value.
I’m not going to waste time with an introduction to unit testing. There are plenty of other resources for that. This article is a handful of practical tips for unit testing real world apps.
Continue reading Java Unit Testing Tips
I just came across this slightly older writing from Patrick about the pain of ActionForms in Struts. I, personally, have not written Struts code. In my last job, I managed some people who were writing Struts code, though. I’m aware of the benefits of MVC, but it really did seem like there was a whole lot of programmer overhead in writing Struts apps. xDoclet seems like one possible solution, but it really makes you wonder if the framework can or should be doing more. WebWork2 sounds promising, and we’re planning to try out both Struts and WW2 for an app we’re just starting.
Here is a way to get something like C# Delegates in Java. A delegate is basically an object representing a bound method. I didn’t realize that C# had this, and it’s a very nice feature that I wish Java had. The implementation the authors have done is pretty good, but it would be nice to have the same kind of syntactic sugar that C# provides here. Maybe J2SE 1.6?
According to the latest Eclipse Project Draft 3.0 Plan, 3.0 Milestone 1 is scheduled to be released June 6th! Of course, their release plan goes all the way up to M5 in November, but still it will be great to start seeing new Eclipse features showing up. Here are the things that interest me most that are committed for 3.0:
- Lots of editor improvements including more typing actions, better integrated key bindings, folding in the editor window and splitting of the editor window to edit different parts of the same document
- Make Eclipse usable as a rich client platform, not just for IDEs. Plug-ins, help system, update manager all will be packaged for use in other programs.
- Support Java and Java references in other files (like JSP and SQLj, and references to classes that appear in xml files)
- Present a logical view of the objects in the debugger (so a HashMap appears as key/value, not just a java.util.HashMap)
The following are some nifty “proposed” items for 3.0, which means they don’t have a specific solution yet.
- Be able to open files outside the workspace! – I can understand why this is tricky (do those files compile? If so, where to?), but it would still be nice to be able to use the Eclipse editor for other, non-managed files.
- HTML widget that works on all platforms
- Automatic synchronization with filesystem changes
- Plug-ins can be added/removed dynamically
- Better interoperability between Swing and SWT
- Support for J2SE1.5 – I really hope generics makes it into an early Eclipse release, because I’d like to start using them. There are all ready reliable ways to compile 1.5 generics for use in current JVMs
Lots of good stuff coming down the line, and the number of plug-ins grows all the time. Eclipse shows just how good an open source project can do when it has a bit of money backing it!