Hi there, I have a framework to announce that was built on top of Wicket
and Wicket-Bootstrap. It applies the Naked Objects pattern to generate HTML
files and the corresponding Wicket Binding for you based on your models.
All the while allowing you to fully stay in control and be able to do what
you are used to with Wicket and the components provided by Wicket-Bootstrap.

More info at the documentation website: http://invesdwin.de/nowicket/
And on GitHub: https://github.com/subes/invesdwin-nowicket

In the documentation I am talking about the difference to Apache Isis.
Mainly the difference is that NoWicket does not aim at going as deep as the
persistence layer for the models and does not want to be a full CRUD
framework. Also explaining what disadvantages that would have for wanting
to stay in control. With NoWicket you actually still have your HTML files
to edit and the Wicket Page and Panel implementations you can customize.
NoWicket just automates the boring coding for most needs and reduces the
amount of SLOC to write by a magnitude.

Could you please check that I make no claims about Apache Isis that
are incorrect?

Thanks!

Reply via email to