Hi!
Thanks. The issue is not only "forgetting to refactor", but it is also
difficult to make reusable components that only have fixed
functionaltity but leave freedom for the designer to position
components. Often when same functionality is needed on another page
that has slightly different layout, it breaks in wicket.
Allowing components to move in a desired range makes components more
reusable. Ofcourse it is even better if you can flexibly define
boundaries of the freedom and thus avoid any security leaks.
**
Martin
2010/11/8 Kent Tong :
> Hi,
>
> I've a blog entry on this issue:
>
> http://www.dzone.com/links/r/scala_exercise_6_tackling_the_wicket_hierarchy_mi.html
>
> definitely not a solution, but just some ideas.
>
> --
> Kent Tong, Msc, PMP, CISSP, ITIL Foundation
> Senior manager of IT dept, CPTTM
> Authorized training for Adobe, Aruba, Cisco, Microsoft, SUN
>
> -
> 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
