Hi,

I think this approach of changing .add or adding a .queue is too radical while the purpose can be achieved in a much simpler way. I think hierarchy of Java code among other things helps considerably with code-readability and should be kept in pace, but also it's strictness sometimes makes one have to change the code for trivial markup change/requirement which is inconvenient.

So I suggest instead of tampering with code hierarchy, let markup override it with some special format in wicket:id - for example both these markups can work with the same java code: <a wicket:id="edit"><span wicket:id="name"/></a> <b wicket:id=":edit:name"/> (<a wicket:id="edit">edit</a>) (wicket:id=":edit:name" means relative path "edit:name" from the panel that owns the markup)

We just check for colon at markup id, resolve the component by relative path, determine it's visibility & enabled-ness the traditional way and render it. For ajax, I guess when rendering components we can check if it has children that have been rendered outside itself, if the child has outputMarkupId enabled just render that too, if not print a warn message that the markup designer has made a mistake there.

What do you think? Does this do what you want? Is there something I overlooked?

Omid

On Mon, Nov 8, 2010 at 8:28 PM, Igor Vaynberg <igor...@gmail.com> wrote: