I've release Tapestry 1.0.0. Huzzah!
If you're doing Java, you need to be using two frameworks:
1) Log4J is the only way to put runtime logging output into your app. It's slick, configurable and very, very easy. Oh, and if you use Tapestry, the built-in Tapestry Inspector allows you to configure Log4J on the fly.
2) JUnit is the balls. Just get diciplined and write a bunch of quick tests to go with your code. Easy as cake.
Latest word is that my article in the Java Report will be showing up a little late, in the July 2001 issue.
Found what may be a good open source, Java, UML tool called ArgoUML.
I haven't checked it out too much, but what I saw was pretty impressive.
I'm beginning to lean the joyrs of Python and wxPython. Maybe I wont be programming in Java for the rest of my life ... certainly not for an GUIs.
As I learn this stuff, I hope to create GUI editors for Tapestry and for Sabertooth.
Things are winding down on Tapestry for the moment. The code is stabilizing and I'm working just on bug fixes, documentation and some improvements to the JBE.
I'm also planning my next framework: Sabertooth. It's yet another approach to accessing database data. It borrows some ideas from NeXT/Apple EOF and J2EE Entity EJBs but is architected to work well in a web application environment.
I once read a quite from someone on the Quake team who said "all computer science is caching" at that's very true.
You win some, you lose some. The Java Report has accepted my article on Tapestry (though I need to put together some performance stats and UML diagrams).
However, JavaOne has turned down my proposal to present Tapestry.
Tapestry 0.2.9 is coming very soon. I really have to figure out when I can just call it "1.0.0".
Release version 0.2.8a of Tapestry just now. A little bit of savage refactoring, and I completed support for localization.
I seem to spend at least as much time documenting things as I do actually coding them.
What's in a name? I'm in the process of changing the name of the central object of a Tapestry application.
Instead of "application", it will now be "engine".
This fixes so much of the documentation! It moves the term "application" out of the real of implementation and back into the real of pure ideas.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!