On 8/16/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
metadata might be good, but dont forget that every call to isvisible() will have to check for metadata to see if its been cached - so this affects every component i think.
yes, but you cannot partial render the enclosure because you have no reference to it in code - it is purely a construct of the markup.
well - the component doesnt know its inside an enclosure - thats the whole idea. but this might not actually cause any problems - i mightve been overthinking.
hmm but how do you get access to the enclosure object? it is only defined in the parent. do you mean you would do componentInsideEnclosure().getParent() ?
i personally dont, but some people might do, component.getParent() and expect a certain parent - but the enclosure is inserted in the markup only so its invisible in the java component hierarchy - might be a bit confusiing i suppose.
awesome, i hope to play with it some as soon as i have time.
-Igor
I've got a first draft ready.
- avoid that label.setVisible() called twice not yet implemented. I
don't like the short variable. We'll keep on increasing the flags and
vars with every release. What about using the MetaData? Need more mem
if used, but only for very few components.
metadata might be good, but dont forget that every call to isvisible() will have to check for metadata to see if its been cached - so this affects every component i think.
- partial render: not sure I understand the problem. If you
(partial-)render the enclosure and all it children, everything will be
as expected.
yes, but you cannot partial render the enclosure because you have no reference to it in code - it is purely a construct of the markup.
If you (partial) render a component inside the enclosure,
the enclosure will be neglected.
Do you have a use case where you want
to partial render a component inside an enclosure?
well - the component doesnt know its inside an enclosure - thats the whole idea. but this might not actually cause any problems - i mightve been overthinking.
- My first draft version does not
enclosure.setVisible(lable.isVisible()) as that would remove the
<wicket:enclosure></wicket:enclosure> tags as well. Instead, if
lable.isVisible() == false, than only the body of the enclosure is not
rendered, but the tags are. You can still enclosure.setVisible(true)
to disable to enclosure as well.
hmm but how do you get access to the enclosure object? it is only defined in the parent. do you mean you would do componentInsideEnclosure().getParent() ?
i personally dont, but some people might do, component.getParent() and expect a certain parent - but the enclosure is inserted in the markup only so its invisible in the java component hierarchy - might be a bit confusiing i suppose.
- The draft version is not enable by default. The IMarupFilter must be
registered as usual. Please see the test case for details.
- This is a draft version only and can be removed if required. I
understand that we didn't have a formal decision yet on whether this
feature should go into core, into extension or not added at all.
awesome, i hope to play with it some as soon as i have time.
-Igor
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
