for the fact that you know Tapestry better.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5686974.html
Sent from the Tapestry - User mailing list archive at Nabble.com
re persisting the object used to iterate the grid
3. You have tied @Persist to onPassivate()
It's at this point we gave up. No point in flogging a dead horse.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp56813
t:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5684938.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tape
m - unless I have code that actually works. Just declaring try
> this and that is not sufficient. Finally, as for time spent, we are all in
> the same canoe. This is the only way this tool gets sharpened.
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nab
we are all in
the same canoe. This is the only way this tool gets sharpened.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5684235.html
Sent from the Tapestry - User mailing list archive at
On Thu, 03 May 2012 15:49:19 -0300, netdawg wrote:
Good grief. O well, that is probably more oxygen for others. Thanks
for you inputs nevertheless - the ones with substance, anyway. As for
"wink, wink, we are already doing magic" - it borders on delusional -
suggesting some
sort of ins
ers - you have perfect right to do that, but that there will more
> footsteps out the door than inpossibly mine too. Good bye.
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5
Netdawg, this is not the first time you've come on the list, been given
good advice, ignored it and done your own hacky thing
This blog post of yours is ignoring every piece of advice you were given on
the list http://crudsqbe.wordpress.com/2012/04/29/tapestry
I can understand thiago's frustratio
lping some and not
others - you have perfect right to do that, but that there will more
footsteps out the door than inpossibly mine too. Good bye.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5684049.html
Sen
t 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 -
-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
On Wed, 02 May 2012 21:28:05 -0300, netdawg wrote:
OK. Lets leave it at that, I guess. Agree to disagree ;-).
1. Polymorphism is not about implementation at all. It is about
interfaces, which is what Components can aspire to be, sort of. In that
case, components, do not get tied to page
t not urgent...as I said...I have found a way
> (or
> a hack? Eye of the beholder ;-)).
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681966.html
> Sent from the Tapestry - User mailing list a
1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681966.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additiona
..but I am already on a roll, so perhaps
will look into later and report back
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681962.html
Sent from the Tapestry - User mailing list archive at
On Wed, 02 May 2012 19:19:43 -0300, netdawg wrote:
For the component to pick up page property would make it "Polymorphic".
Regarding your mention of polymorphism and quoting Princess Bride, "I do
not think it means what you think it means.".
Components, for instance, can then just be a "s
On Wed, 02 May 2012 18:46:59 -0300, netdawg wrote:
BTW, I just posted a citation which describes the
componentResources...which
is already able to pull up the pageName...this is very useful in
authoring solid code at the page level. Why would componentResources
have the
pagename attribut
meters are - in case of a
circle it would be a radius, for rectangle - two sides etc.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681782.html
Sent from the Tapestry - User mailing list a
meter...?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681722.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscri
On Wed, 02 May 2012 17:12:38 -0300, netdawg wrote:
It violates the self-contained principle for components very badly.
Sorry - Disagree. Components are NOT meant to be "self-contained". They
are supposed to govern sub-components.
[Citation needed]
In fact,
prop:componentResources.pageNa
On Wed, 02 May 2012 16:59:41 -0300, netdawg wrote:
By parameters do you mean - pass dynamic run-time (request) parameters
to a page that is picked up instead by the containing component?
No. Tapestry component parameters. There's no reason for you to use
request attribute in a pure Tapestr
fault";
> }
>
>
> Index.java is now empty
>
> But Index page will have to be called by invoked index?pageProperty=
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp568
In other words, why is this "bad"? What specific dangers, problems do you
see? I see only more convenience. If, by bad, you mean in poor taste -
just don't use it.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informe
ed benefit,* if the page class is ever renamed or moved to a different
package, the pageName property will automatically adjust to the new name*.
...This is what I am talking about.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-
asking to extend it further
>>> Question does not make sense...
pages, like Index, are not inheriting layout etc, from component Layout?
What am I missing?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class
Index page will have to be called by invoked index?pageProperty=
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681501.html
Sent from the Tapestry - User mailing list archive at
By parameters do you mean - pass dynamic run-time (request) parameters to a
page that is picked up instead by the containing component?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681479.html
Sent from the
On Wed, 02 May 2012 16:33:05 -0300, netdawg wrote:
This may be a somewhat of a useful stand-in for the pageProperty...
${prop:componentResources.pageName}
It gets you the page name...and can be put in the component.
However, something like this would be useful
${prop:componentResources.pageName
On Wed, 02 May 2012 16:16:14 -0300, netdawg wrote:
Basically, is there is a way for a component to "inherit" properties of
child component (page)?
Pages cannot be child of components, so your question doesn't make sense.
For communication between pages, components and mixins, you can use
p
worthy???
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681430.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To
It might be possible but it's not recommended ;)
Can you just pass a property from the page to the layout?
http://wiki.apache.org/tapestry/Tapestry5Layoutcomponent
nu for the individual pages.
Basically, is there is a way for a component to "inherit" properties of
child component (page)?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397.html
Sent from the Tapestry - User
32 matches
Mail list logo
