We're choosing an item from a list and then using ajax to populate a
view of the item, together with a listview of purchasable details.
For any given item there may or may not be images. Either managing
the relevant components in a page-level collection or using a visitor
to find them works. The
How about using an IVisitor to call setVisible() on the image
components? That way, you wouldn't need to keep an explicit reference
to those image components. You could trigger the visitor in
onBeforeRender() and you could use a marker interface to identify the
image components whose
On Sep 7, 2007, at 8:52 PM, Carlos Pita wrote:
You can also make the components to hide implement some listener (or
just marker) interface X and then do a visitChildren traversal from
page.onBeforeRender as follows:
visitChildren(X.class, new IVisitor() {
public Object component(Component
I want to make a few parts of my page visible or not in a consistent
manner -- i.e. based on the same true/false result, which I derive
from my model. Can I wrap the relevant components in
WebMarkupContainer without adding a matching div tag to my markup?
Thank you,
Scott
--
Scott Swank
no, but you can try wicket:enclosure tag. see javadoc on Enclosure.java
-igor
On 9/7/07, Scott Swank [EMAIL PROTECTED] wrote:
I want to make a few parts of my page visible or not in a consistent
manner -- i.e. based on the same true/false result, which I derive
from my model. Can I wrap
you can prob port enclosure to 1.2.6 yourself if you wanted it badly
-igor
On 9/7/07, Scott Swank [EMAIL PROTECTED] wrote:
Pity we're not on 1.3 yet. Thank you though.
Scott
On 9/7/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
no, but you can try wicket:enclosure tag. see javadoc on
well, thats kinda the point of the enclosure...
it lets you group components together inside it, and let one of those
components drive the visibility of the entire enclosure
-igor
On 9/7/07, Scott Swank [EMAIL PROTECTED] wrote:
I could, but it's kind of the opposite of what I want. I want
I get what you're saying, but the images in question are scattered
across the page rather than in one place that could simply be
enclosed. Thank you none the less, I do appreciate the insight.
Cheers,
Scott
On 9/7/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
well, thats kinda the point of the
Can't you just call webmarkupcontainer.setRenderBodyOnly(true) ?
-Matej
On 9/7/07, Scott Swank [EMAIL PROTECTED] wrote:
I get what you're saying, but the images in question are scattered
across the page rather than in one place that could simply be
enclosed. Thank you none the less, I do
Matej,
My issue isn't that the div is rendered, but rather that I have to add
it to the html file in the first place. I think that I could
implement this as a Behavior, but for this problem I just went ahead
and added div tags around the relevant components.
Thanks again,
Scott
On 9/7/07,
10 matches
Mail list logo
