well, that is not really what wicket does right now.
i think it would be interesting to tie the markup + code more tightly
together, to have the compiler already check for correctness, instead of
runtime.
for example warp-widgets ( http://code.google.com/p/warp-core/ ) does this
in an elegant way at compile-time, using MVEL ( http://mvel.codehaus.org/ )
*i have not thought it through*, but it may be possible to annotate the
html like warp-widgets does, to tie the wicket ids to constants/enums and
keep everything else(pages/panels) in java code the same.
this could be a typesave alternative to wicket:id, so you will not be able
to compile if you didn't supply the enum.
@Wicket(id=MyWebPage.BLA)
<p>Some dummy labelText</p>
or ...
@WicketRemove
<li>additional BulletPoint</li>
i should do a proof-of-concept when my project is finished :)
best regards
andreas
On Tue, 17 Feb 2009 08:52:01 +0000, kan <[email protected]> wrote:
> I mean if you have a wicket:id="abc", it will generate class with...
> emm... not sure, say method "getAbc()" which will return an object
> which represents an element, so it can be bound to a Component. So, in
> java-code you can use only elements which are actually exist in
> html-markup.
> Maybe something similar then set of java classes are generated for wsdl
or
> xsd.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
