You have a big problem when a class depends on the behavior of a
sub-class during construction time. This is because sub-classes are
initialized after the initialization of the base-class. When there is no
dependency, there is no problem.
So, although I recognize Gili's point in general, I
The traffic on this list is way up and above my reading capacity. Still
I'd hate to miss the announcements. So, what do you think?
Erik.
---
SF.Net email is Sponsored by the Better Software Conference EXPO
September 19-22, 2005 * San
You could try:
page.setVersioned(false)
I'm not a wicket-guru though.
Erik.
---
SF.Net email is Sponsored by the Better Software Conference EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile
Thanks Martijn.
Erik.
Martijn Dashorst schreef:
That is the thing: the model is your POJO and the choice components
set the value on your object. I'll add it though. I think that is
pretty unclear at the moment. The following text is something I just
wrote: .
Excellent. This is exactly the kind of stuff I was waiting for :)
Could you write 2 lines for the choise components on how to read the
selection from the model ?
Regards,
Erik.
Martijn Dashorst schreef:
All,
I've started working on a reference guide yesterday, and I've got my
first
I hate to answer my own questions, but after an hour of coding, I found
out it's not possible:
wicket.markup.MarkupException: Markup for a panel component has to
contain part 'wicket:panel'
[markup = file:/../classes/zout/site/menu/SimpleMenuItem.html, index
= 3, current =
I am not even sure the following interface will be used at all, but
maybe I can contribute in a small way with my small comment on the names.
interface IteratorProvider{
int size();
Iterator iterator(int start, int minCount);
}
This very similar to the Java 5 Iterable interface.
What
Having 2 versions, one for 1.5 and one for = 1.5, is I guess out
of the question as well? (like commons-collections)
It would be great to at least javadoc stuff as if it were developed
for 1.5.
Erik.
As a framework we can't do that yet i am afraid.
i think even 1.2 will be to soon. As
It should be:
listItem.setRenderBodyOnly(true);
as the list items are the components that you are actually repeating /
rendering.
Eelco
Ah yes, that works splendidly.
Thanks,
Erik.
---
SF.Net email is sponsored by: Discover Easy
id=wicket-items is very old. Shouldn't be there. Where did you see it?
They are in the javadoc of wicket.markup.html.list.ListView.
Yep, need more docs. Did you take a look at the WIKI?
http://wicket.sourceforge.net/wiki/ It's the best place to start right
now. And this list ofcourse...
Eelco Hillenius schreef:
I tried span wicket:id=menuItems with
this.getSettings().setStripWicketTags(true); in the application
constructor. However, there is still a span element rendered. I
want to get rid of those as well as it plays havoc with my css styles.
Not sure whether I understand
Hmm.. why don't you use just
div class=MenuBlockTitle wicket:id=title_title/div
The spans in the div are not necessary.
I shortened the original HTML for the list. Forgot this one.
---
SF.Net email is sponsored by: Discover Easy
Igor Vaynberg schreef:
In your MenuItems component call setRenderBodyOnly(true)
Igor
It does not work. I still see the spans in my output. Is it a bug? I am
using wicket-kickstart 1.01.
This is my code:
ListView menuComponent = new ListView(menuItems, menuItems) {
+1
Wicket should not depend too much on the cleverness of the average
programmer, especially when we talk about making code thread safe. I
have seen this being underestimated too often already.
Regards,
Erik.
---
SF.Net email is
Hi,
Attached is a
proposed change of the file
\mmdocs\reference\taglib\listprovider.jsp.
Changes:
- Added
documentation on comparator attribute including example.
Regards,
Erik.
listprovider.jsp
Description: Binary data
1001 - 1015 of 1015 matches
Mail list logo