On Thu, 19 Feb 2015 17:17:01 -0200, Sumanth <roasteddra...@gmail.com>
wrote:
Hello George, Hello Thiago,
Hi!
Well I can certainly try the way you have suggested, but wouldn't it be
better tif tapestry can handle it? Because, I know that we need to
specify id for the zone when we use it, so generally a static client id
will
be given to these component eg : <t:zone t:id="Hello" id="hello" > but if
the zone is inside another component then shouldn't tapestry generate
unique id for this zone like componentid_zoneid?
Tapestry does generate the unique client-side ids for Zone and other
components when rendering the template. The problem is that it doesn't
when handling events. It shouldn't, because, to do that, Tapestry would
need to simulate a rendering when handling the event. Tapestry 4 did that.
It was the very much misunderstood "rewind phase". It made understanding
the framework more difficult and had worse performance. Tapestry 5 is very
better off without it.
If some one is developing a component he would not have imagine a
condition where his component will be used on the same page twice?.
Yes, the developer should think of this situation because it's very common.
So suppose I use a component which is developed by someone else, then
will it not cause problem because he did not include dynamic id's for a
zone
inside the component?
Probably yes, and this should be considered a badly implemented component
for not using Zone correctly.
I might be wrong in my understand but a component should work like a
black> box to me right?.
Yes!
<t:hisComponent t:id="his">, so whether there is zone
inside the component or not, it should just behave like a black box to me
right?
Yes. The component author should write his component correctly.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
