Hmm,

I still don't understand the benefit of a automatically generated id.
I mean it is generated and I can reference it only in js if I know the
algorithm. Of what benefit is it than?
hmm, seems we're talking about different things. I want a way to ask a component for the document id it will render so I can use that in generating javascript code referring that components markup. Use case is the dropdownchoice again; I need the dropdownchoice to render a id attribute so it can be referred in the browser later on.

How many components in average require an id which gets referenced by
JS? Does it realy help that much to automatically generate them?
Everytime you want to touch component based markup using client side javascript it's needed. A way to have components render ids is a basic requirement for using them (as they are) in client side javascript. So, yes :)

you just suggest behaveours as wells. Would it make sense to have
application wide behaviours which get applied to all components and
one of these behaviours would than implement it? I actually prefer
that over your suggest Interface.
Yep, the behaviour idea is actually newer than the "I need a id" problem. This is another nice usecase for behaviours; there could be a DocumentIdRequired behaviour which would get the id into the components markup. This behaviour could even be requested by other behaviours (which want to do advanced things at client side with the component). But as id generation is a pretty basic thing for javascript it still could make sense to have components doing this by default...

Regards,
Ralf


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to