Thanks for the testimonial!
Hopefully from now on (although no promises just yet) the internals of Wicket RAD will stay somewhat stable, so there will be less work to update.
I think it is getting to a point where I am quite happy about the internals of the framework, although there may still be some minor kinks and changes to work out here and there.
I will at least try to document changes in the API's better from now on.
(a point regarding the stability of the codebase would be that 0.4 is the first release that has been tagged in Subversion and put in a Maven repo, whereas previous releases where just code snapshots of a reasonably stable state.
Also, from a personal perspective, I feel less stressed these days about "having to make critical changes and features" :) ).
oyvindj wrote:
Hi,
I just released first release of my application, using Wicket RAD. Just wanted to state for anybody looking into Wicket RAD that I find it very useful.
It really relieves the developer from a lot of tedious coding, and keeps all the important information where it logically belongs for most use cases (in the bean).
I've also found it to be quite stable and error free. Still some refactoring to do updating the code between each release though :-)
I can also add that I am only using the presentation part of Wicket RAD (not for the persistence). I think that is where Wicket-RAD really shines. I use Wicket-RAD for every form and list in my application, not only for the bean/forms to be persisted.
Unfortunately my app is for internal use only so no demo or source yet...
Happy Wicket-RADing!
Oyvind
