Hi,
Actually haven't used or looked into WWB too much to be honest.
I think there are some similarities, although at the same time some divergent design choices.
Some of them, that I think exists (take this with a pinch of salt, as my WWB knowledge is somewhat limited):
- WWB seems to be very bean focused, Wicket RAD is currently bean focused too, although the internal architecture makes it simple to add implementations for other types of datasources (database tables, forms from JPA annotations or just plain beans instead if Wicket RAD annotations etc).
- WWB seems to take a "layout by configuration" approach (from what I saw a long time ago), whereas Wicket RAD takes a layout by composition and extension approach.
I think to some degree they "scratch the same itch", I think the long term goal of Wicket RAD is basically to off load a lot of tedious and repetitive markup work, so developers can just put together pages with pre-made components (such as generated forms etc).
As I said, haven't looked into WWB too much, and I haven't spoken to the guys behind it, but in the future I could definitely see working with them to pick of the best pieces of each framework - I think a healthy degree of competition and collaboration combined could make the Wicket community stronger (competition to get out the best ideas, collaboration to implement them).
dtoffe wrote:
Hi !
I've used WWB a bit for some time, never tried WR yet. From the project's descriptions, it looks like both are more or less "scratching the same itch", that is, to allow quickly building user interfaces based on the data model and some configuration mechanism (annotations, properties), and to ease the access of that data (Hibernate, JPA, Databinder...).
So I dare to ask, what are the main similarities and differences between both projects ? Are both heading the same way, or is there any specific divergence in the future plans ?
Best regards,
Daniel
