I suppose so.. Well, at least it's a loophole for big chucks of readonly data.
Thanks for your replies!
Groet,
Vincent
On Jul 26, 2010, at 17:22, Igor Vaynberg wrote:
> no, this will not work for the larger usecase. like i mentioned
> before, if you place links or textfields or anything but la
no, this will not work for the larger usecase. like i mentioned
before, if you place links or textfields or anything but labels into
listitems they will not work.
-igor
On Mon, Jul 26, 2010 at 3:41 AM, Vincent Lussenburg
wrote:
> Hi Igor,
>
> Excellent suggestion! It took some experimenting, but
no, this will not work for the larger usecase. like i mentioned
before, if you place links or textfields or anything but labels into
listitems they will not work.
-igor
On Mon, Jul 26, 2010 at 3:41 AM, Vincent Lussenburg
wrote:
> Hi Igor,
>
> Excellent suggestion! It took some experimenting, but
Hi Igor,
Excellent suggestion! It took some experimenting, but we managed to get it
to work.
add(new PropertyListView("month", new
XListViewModel(x)) {
{
setReuseItems(false);
setVersioned(false);
}
@Override
what about onDetach() ?
-igor
On Thu, Jul 22, 2010 at 6:17 AM, Danny van Bruggen wrote:
> No, we can't change the component tree in onAfterRender - Wicket
> complains that it cannot increase the page version after rendering.
>
> On 7/21/10, Vincent Lussenburg wrote:
>> I remember trying that, b
No, we can't change the component tree in onAfterRender - Wicket
complains that it cannot increase the page version after rendering.
On 7/21/10, Vincent Lussenburg wrote:
> I remember trying that, but getting slapped by wicket for trying to change
> the component tree after rendering.. Or am I mi
I remember trying that, but getting slapped by wicket for trying to change the
component tree after rendering.. Or am I missing something?
We'll doublecheck it tomorrow.
Groet,
Vincent
On Jul 21, 2010, at 18:37, Igor Vaynberg wrote:
> if the data is strictly read-only and does not contain any
if the data is strictly read-only and does not contain any links you
can try removing the list items in afterrender()
-igor
On Wed, Jul 21, 2010 at 7:50 AM, Danny van Bruggen wrote:
> Hello all,
>
> We're developing a non-Ajax application that displays a bunch of big
> tables - about five column
Hello all,
We're developing a non-Ajax application that displays a bunch of big
tables - about five columns, 300 rows. Since session size was
increasing a lot, we looked into the cause of it, and (after making
everything detachable and switching to PropertyListModel) found out
that the ListItems o
