Perhaps this is what you mean by "any level within given Panel-type
element",
but would this not screw up making components?
The hierarchy is rather important for this - unlike JSP, etc where you
just dump data references in a "page response"
Components are one of the things that makes Wicket so nice.
On 11/4/10 1:13 PM, Martin Makundi wrote:
I propose "Free Wicket" from component-hierarchy hell
We have discussd before that Wicket has unnecessary binding to
wicket:id and component hierarchy
[http://www.mail-archive.com/users@wicket.apache.org/msg53941.html].
I think I found a simple solution: "wicket:id" should be allowed to be
on any level within given Panel-type element. User has freedom to
position components and change html layout.
What you think?
Old wicket applications can be automatically refectored to have unique
ids. Currently the wicket hardcoded component hierarchy slows down
development and is totally unnecessary.
https://cwiki.apache.org/confluence/display/WICKET/Wicket+1.5+Wish+List
**
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
