Hi there!
There are some things in Wicket I am missing and I think they could improve the
framework a lot.....
But just some small background first:
In my opinion the most important things in a web application are:
- as few lines of code as possible, as many as really necessary
- separation of design and web application code and logic
- if a webapplication changes in the design or some small items are added this
should be possible without needing a java developer....
Therefore I would like to suggest more intelligent templates in Wicket:
1. Pass parameters inside of wicket components eg:
<div wicket:id="myComponent" paramA="blabla" paramB="blabla2"></div>
and make them accessible in the Java code.
This is a way to customize and reuse components purely by editing templates
2. Make Strings/Labels accessible directly in templates....to avoid redundant
code like this:
add(new Label("indexTitle", .....) and instead allow to add properties directly.
3. Pick up components automatically without needing to add them in the Java
code:
add(new LastPostsPanel("lastPostsPanel"));
add(new NewsPanel("newsPanel"));
This could be matched automatically
I think Wicket could be better without so much redundant copy&paste code...by
improving templates....
Thanks for listening...
Toby
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
