Yeah, I'm pretty sure that's fixed in one of the style tweaks I made a
few weeks back, but there hasn't been a release since then.
On Mon, Dec 31, 2012 at 9:28 AM, Michael Gentry wrote:
> An "interesting" documentation glitch is the header for the
> ComponentResourcesCommon
> (and Locatable) box
An "interesting" documentation glitch is the header for the
ComponentResourcesCommon
(and Locatable) box reads like this (at least in Chrome):
"Methods inherited from interface org.apache.tapestry5."
"ComponentResourcesCommon" is a hyperlink in the same color as the box
background, so you don't s
bobharner wrote
>
By the way, just in case it helps someone. We have many pages passing "this"
page to the components. Now I know it can be retrieved using
ComponentResources. But, in order to avoid changing everything at once, I
figured out a way to let my component receive the page parameter (s
fmaylinch wrote
> It's strange because ComponentResources doesn't seem to have that
> property:
Oh yes it does; it comes from ComponentResourcesCommon.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Access-this-page-object-from-the-template-tp5719073p5719080.html
Sent f
bobharner wrote
> Per http://tapestry.apache.org/link-components-faq.html it's pretty
> easy to generate a link to the current page:
>
> refresh page
>
> Similarly, you should be able to do this:
>
Thanks!
It's strange because ComponentResources doesn't seem to have that property:
http://tape
Per http://tapestry.apache.org/link-components-faq.html it's pretty
easy to generate a link to the current page:
refresh page
Similarly, you should be able to do this:
On Mon, Dec 31, 2012 at 7:40 AM, fmaylinch wrote:
> Chris Poulsen wrote
>> Would it not be easier to simply inject Component
Chris Poulsen wrote
> Would it not be easier to simply inject ComponentResources in your
> component class and use it for current page?
Thanks! I didn't thought of that...
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Access-this-page-object-from-the-template-tp5719073
Hi,
Would it not be easier to simply inject ComponentResources in your
component class and use it for current page?
--
Chris
On Mon, Dec 31, 2012 at 12:26 PM, fmaylinch wrote:
> Hello,
>
> This might be a stupid question but... can we access the page object from
> the template (to pass it to
