On Mon, 2007-06-04 at 17:21 +0700, Ivan Dubrov wrote:
> Nick Westgate wrote:
> > Hi Martin.
> >
> > A typical way to do this in previous Tapestry versions is to have
> > some simple logic functions in your component class to provide a
> > boolean result ("this link is to the current page") which is
Nick Westgate wrote:
> Hi Martin.
>
> A typical way to do this in previous Tapestry versions is to have
> some simple logic functions in your component class to provide a
> boolean result ("this link is to the current page") which is used
> for each link's disabled parameter, and to select a string
Hi Martin.
A typical way to do this in previous Tapestry versions is to have
some simple logic functions in your component class to provide a
boolean result ("this link is to the current page") which is used
for each link's disabled parameter, and to select a string supplied
to an informal CSS "st
On Fri, 2007-06-01 at 08:48 -0700, Howard Lewis Ship wrote:
> You have to inject your ComponentResources.
>
> There are methods for generating page render links and component action
> links as part of the ComponentResources interface.
Great!
What's then the intended way of rendering the component
You have to inject your ComponentResources.
There are methods for generating page render links and component action
links as part of the ComponentResources interface.
On 6/1/07, Martin Dietze <[EMAIL PROTECTED]> wrote:
Hi,
I'm trying to create a component for a navigation element
which contai
