I found out a menu component was already available in Tomahawk. It would be
great if it was possible using Clay to build a new Renderer in case the html
generated is not alright for any reason (here for example we have to respect
XHTML strict so it's always a concern) but I guess it's not possible
On 12/6/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
I found out a menu component was already available in Tomahawk. It would
be
great if it was possible using Clay to build a new Renderer in case the
html
generated is not alright for any reason (here for example we have to
respect
XHTML
I have no idea sincerely. It is a very good point indeed. I was just
throwing this idea because autogenerated content sometimes is a pain in the
a** and writting a class to output content doesn't seem right to me.
On 12/6/05, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/6/05, Alexandre
Guess what?
I need an if component now (to change some visual attributes). Of course,
I could code the component but I really prefer to do it in a declarative way
à la JSTL. Tags file weren't invented for nothing afterall so I guess Shale
should follow this direction too. I'll probably try to
You will probably need to look at using the rendered attribute of the
component. This is the JSF way of changing the visibility dynamically.
rendered=#{mybean.isSomethingVisible}
set name=rendered value=#{mybean.isSomethingVisible}/
Gary
-- Original message --
Guess
I know about rendered but it's not about changing the visibility but
changing the style class. In fact I want to add 'active' to the value of a
menu element style class, depending of wich one is activated.
I think I could do it with rendered but my concern is to end up with a lot
of non desired
On 12/5/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
I know about rendered but it's not about changing the visibility but
changing the style class. In fact I want to add 'active' to the value of a
menu element style class, depending of wich one is activated.
I think I could do it with
Look great to me. I am just wondering how sessionScopeVar is working? Is it
like the var argument in JSTL?
Yep, it's like the var. Maybe it would be better to name it var and provide
a scope attribute for request or session. I went with session to avoid the
same questions about the
Yeah but this type of list is not supported unfortunately. I guess I will
have to create a new display for the list component.
But I still think forEach component is a must when you need to create a new
component wich is just an aggreation of some other components.It's a good
mean to provide an
On 12/3/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
Yeah but this type of list is not supported unfortunately. I guess I will
have to create a new display for the list component.
But I still think forEach component is a must when you need to create a new
component wich is just an
I think they are quite the same cases, the second one being a subset of the
former.
On 12/3/05, Ryan Wynn [EMAIL PROTECTED] wrote:
On 12/3/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
Yeah but this type of list is not supported unfortunately. I guess I
will
have to create a new display
I created a ticket that demonstrates a dynamic subtree in a for loop.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37773
Please take a look to see if this would be sufficient.
Gary
-- Original message --
On 12/3/05, Alexandre Poitras wrote:
Yeah but this type
Look great to me. I am just wondering how sessionScopeVar is working? Is it
like the var argument in JSTL?
By the way, what I like about this approach is that we don't have to hide
everything behind JSF components. I was wondering why I would need to write
a list component while in fact a list or
Hi,
I am wondering right now how is it possible to generate a dynamic data
list component (dl) since no faces package offer it. First, I taught
no problem, Clay solves this situation quite easily but right now I am
stuck. I don't know how to make a loop to render all list elements.
Tapestry
Hi,
I am wondering right now how is it possible to generate a dynamic data
list component (dl) since no faces package offer it. First, I taught
no problem, Clay solves this situation quite easily but right now I am
stuck. I don't know how to make a loop to render all list elements.
On 12/2/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
Hi,
I am wondering right now how is it possible to generate a dynamic data
list component (dl) since no faces package offer it. First, I taught
no problem, Clay solves this situation quite easily but right now I am
stuck. I don't know
16 matches
Mail list logo