Can be of some use for wicket ?
http://www.theserverside.com/news/thread.tss?thread_id=44804
https://bean-properties.dev.java.net/
saki
On 12/12/06, Petr Sakar [EMAIL PROTECTED] wrote:
On 11/29/06, Johan Compagner [EMAIL PROTECTED] wrote:
what makes a formcomponent a formcomponent?
That, of course, is the main question :) But not an easy one,
certainly not to extract a robust interface from it. The component
like I
wicket:panel and
wicket:border tags? What about a border fragment attached to a text
field?
It also might be quite tedious to implement. More people have thoughts
on
this?
Eelco
On 12/12/06, Petr Sakar [EMAIL PROTECTED] wrote:
On 11/29/06, Johan Compagner [EMAIL PROTECTED] wrote:
what makes
Question / Idea:
If I undestand it correctly, currently component hierarchy is build based
on markup. How about to do it other way round ? For component hierarchy
created in your java code lookup the markup ?
saki
/3/06, Petr Sakar [EMAIL PROTECTED] wrote:
Question / Idea:
If I undestand it correctly, currently component hierarchy is build
based
on markup. How about to do it other way round ? For component hierarchy
created in your java code lookup the markup ?
saki
want the
same thing but i want to use the AjaxFallBackLink? what then?
any kind of link we have now in core or extentions i could use the label
part.
johan
On 10/26/06, Petr Sakar [EMAIL PROTECTED] wrote:
Hi,
I do not follow current development on 2.0, but it seems to me, that
link
our project, and it works nice.
It saves a lot of work ...
saki
Martijn
On 10/27/06, Petr Sakar [EMAIL PROTECTED] wrote:
Hi,
currently (wicket 1.2) if I want to make component with own markup, I
must
extend Panel, or override some method to provide markup.
Can you use as well interfaces