Del.icio.us has been down for a while. I use it for my public bookmarks, which are listed on the side of this blog. Here is a post with some recent random things that I would bookmark if I could.
The departure of the hyper-enthusiasts - "The Java hyper-enthusiasts have left the building" (along [...]
There is recent interest in consolidating Java frameworks with similar approaches. WebWork is joining Struts, which surprised me. Along the same lines, the Java Web Alignment group brings together many big players in the Java framework space:
The Java web framework landscape has become quite fragmented; the purpose of this group is to explore [...]
Ok, Greg Beaver's work on channels has resurrected my interest in PEAR. I am interested in providing WACT on a PEAR channel and I'd like to better integrate WACT with some PEAR packages. My primary concern is over the installation implications.
I didn't find a "powered by PEAR" section on the PEAR website. [...]
I ran across this O'Reily article about SpikeSource today. Very interesting.
They have released a coverage reporting tool, Spike PHP Coverage, for PHP that works with XDebug coverage data. It works with Simple Test and it seems to be able aggregate the results of remote test runs, such as for web based tests. [...]
My last WACT post drew a couple questions from Marcus Baker:
Do you have a release date planned for the next version?
Ah, the release date question. We are certainly overdue. Here is where things stand.
The core framework in CVS is in very good shape. We have 3332 passing tests and 5 failing tests. [...]
This post shows some bad design elements in WACT and discusses how to improve them. It lists some related bad code smells in the WACT template compiler. It is a non-trivial example of refactoring in an established application and an illustration of OO design issues.
related files:
treebuilder.inc.php
parserstate.inc.php
tagjudge.inc.php
tagdictionary.inc.php
input.tag.php
The TreeBuilder and ComponentParsingState classes may need to [...]
Jon Ramsey came up with a continuous integration tool called Rephlux. Rephlux periodically checks out your code from CVS and runs your unit tests on it. It produces a RSS feed of test failures and a RSS feed of CVS revisions. How cool is that?
In the future it should be possible to [...]
All Posts
