may it be enough just create an independent simple
html-code-processor-to-wicket-java-code-tool, that would auto-generate that
tedious code you would like to avoid? a simple java-class-processor-tool may
help for that... possible an eclipse-wicket-plugin-tool, if it doesn't
already exists...
On Thu, Nov 4, 2010 at 11:13 PM, Martin Makundi <
martin.maku...@koodaripalvelut.com> wrote:
> Can you see the matrix?
>
> ;)
>
> If you have:
>
> <html>
> <form wicket:id="form">
> <input wicket:id="input" .../>
> </form>
> </html>
>
> public class MyPage extends WebPage {
> public MyPage () {
> add(new Form("form"));
> add(new TextField("input", model)); // Wicket could
> automatically handle parse hierarchy from markup
> }
> }
>
> **
> Martin
>
> 2010/11/5 Martin Makundi <martin.maku...@koodaripalvelut.com>:
> > 1. I want freedom inside panels.
> >
> > 2. Doubly defined hierarhices are redundant. Server-side hierarchy can
> > be automatically deduced from markup hierarcy. Such tasks should be
> > done by COMPUTER. Not coder.
> >
> > **
> > Martin
> >
> > 2010/11/5 Jonathan Locke <jonathan.lo...@gmail.com>:
> >>
> >> I think if you find component hierarchies to be "hell", you probably
> aren't
> >> using Wicket right. Break things down into small reusable chunks using
> >> Panels and you will find everything gets much, much easier.
> >> --
> >> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Free-wicket-from-component-hierarchy-hell-tp3027705p3027881.html
> >> Sent from the Users forum mailing list archive at Nabble.com.
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>
