I officially give up. You're using wrong definitions of concepts, and the
consequence is that just you will understand what you're talking about.
And you can't read my mind to know what I'm thinking. You have proven
nothing beyond the fact that you don't know what polymorphism is. In a
component, using ComponentResources.getPage() or getPageName() you can
figure out in which page the component is, even if this is a bad approach
in most situations. People already do many magical things (Taha, wink! ;))
with Tapestry the way it is. If you explained better what you want to do
we'll be able to tell how you implement the Tapestry way. I'm not sure
I'll take the time, though.
On Thu, 03 May 2012 14:21:49 -0300, netdawg <net.d...@yahoo.com> wrote:
Thiago, I perfectly understand where you are coming from. But it is
hardly
defensible. And, I suspect you know it. I have just proven to you
polymorphic behavior of components using just pageName. Imagine what
else
can done, in menus alone, with more visibility - multi-level drill-downs
etc. The possibilities are simply fantastic. If Tapestry, cannot (or
will
not) do it - there are other frameworks who will. Waving your resume,
or
credentials, is not going to help in the face of sheer power of logic, or
the market. If you do not want to call it Polymorphism - fine - call it
sometihng else. I was using that term loosely to convey some sense of
different behavior based on what page the component is templating. The
objective here is to enhace that behavior, not block the very
consideration
of it.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5683836.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
