You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Marco Springer <ma...@glitchbox.nl> on 2013/03/26 16:07:17 UTC
Adding a large amount of MarkupContainers into the ListView or RepeatingView
Hi,
Lets say I have about ~100.000 of MarkupContainer objects that I want to put
into a ListView or RepeatingView.
This works fine functional wise... It's rather slow though.
It boils down to:
MarkupContainer:
1309 private Component put(final Component child)
1310 {
1311 int index = children_indexOf(child);
1312 if (index == -1)
1313 {
1314 children_add(child);
1315 return null;
1316 }
1317 else
1318 {
1319 return children_set(index, child);
1320 }
1321 }
and the call to "children_indexOf(child)" where it loops over all it's
existing children and compares the id's until a match is found.
With an increasing amount of children this can get rather slow...
I though off overruling some functionality in the MarkupContainer class since
I'm sure that for this list of items the children will be unique in their id
and don't need that lookup, and overruling the "put" or "children_indexOf"
function would give me enough power to skip that performance impacting part.
But most functions have private access, leaving me nothing to control the
adding of child components to a MarkupContainer.
Does anyone else have experience with adding rather large quantities to
something like the ListView and/or RepeatingView?
Or is there another way of rendering this large amount of containers?
Thanks in advance.
Kind regards,
Marco
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Eric Jablow <er...@gmail.com>.
On Tue, Mar 26, 2013 at 5:33 PM, Eric Jablow <er...@gmail.com> wrote:
> rates during the Crimean War, and Miraud's chart of the Napoleon's March to
Minard, darn it.
> Respectfully,
> Eric Jablow
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Eric Jablow <er...@gmail.com>.
On Tue, Mar 26, 2013 at 5:11 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> On Tue, Mar 26, 2013 at 2:00 PM, Marco Springer <ma...@glitchbox.nl> wrote:
>>
>> On Tuesday 26 March 2013 13:48:05 Igor Vaynberg wrote:
>>> On Tue, Mar 26, 2013 at 1:31 PM, Marco Springer <ma...@glitchbox.nl> wrote:
>>> > Rendering the 287 years
>>>
>>> pretty sure gantt charts didnt exist 287 years ago... :)
>> who talks about the past! the future baby! 26 Feb 2013 - 26 Feb 2300 :)
>
> thats some optimistically farsighted planning :)
No, not GANTT charts. But the first recognizable data visualization
graphs date back
to William Playfair around 1786. These included the forerunner of the
pie chart.
In the 19th Century, there was Florence Nightingale's coxcomb charts of disease
rates during the Crimean War, and Miraud's chart of the Napoleon's March to
and from Moscow. (Yes, I took Tufte's course.)
Respectfully,
Eric Jablow
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Igor Vaynberg <ig...@gmail.com>.
On Tue, Mar 26, 2013 at 2:00 PM, Marco Springer <ma...@glitchbox.nl> wrote:
>
> On Tuesday 26 March 2013 13:48:05 Igor Vaynberg wrote:
>> On Tue, Mar 26, 2013 at 1:31 PM, Marco Springer <ma...@glitchbox.nl> wrote:
>> > Actually, the performance problem was in the first row, well actually the
>> > header that was rendering all days in a week/month/year.
>> >
>> > Each data row itself has a lot less items.
>> > Each row has items that are absolutely positioned within the relatively
>> > positioned row. Each item can span over multiple days/week/months or even
>> > years, depending on the task duration.
>> >
>> > Doing this instead of rendering divs for each day saves a lot of
>> > calculation on the server side and a whole lot less html on the client
>> > side.
>> > And this creates other nifty possibilities like making the item divs
>> > resizable and draggable in that row with bound ajax calls to those
>> > actions.
>> > For showing a grid I've done some background images that match the zoom
>> > level, since each day is static in width.
>> >
>> > I've thought about lazy loading the rows that where outside of the
>> > scrollable view, since I indeed have a scrollable view.
>> > But that's something for the future.
>> >
>> > Rendering the 287 years
>>
>> pretty sure gantt charts didnt exist 287 years ago... :)
> who talks about the past! the future baby! 26 Feb 2013 - 26 Feb 2300 :)
thats some optimistically farsighted planning :)
>>
>> -igor
>>
>> > , e.g. 104k~ ish days, did render eventually and the server
>> > and browser didn't choke, but the div with was about 5M px width wide, so
>> > that was nonsense :P
>> >
>> > On Wednesday 27 March 2013 05:25:40 Bernard wrote:
>> >> Hi,
>> >>
>> >> AFAIK the solutions for large numbers of cells in GUI frameworks are:
>> >>
>> >> 1) Do not render cells that are not in the scrollable view
>> >> 2) Create components only per once row or column and provide cell
>> >> renderers. See javax.swing.table.TableCellRenderer
>> >>
>> >> With these approaches there is basically no limit to the amount of
>> >> data that can be displayed on the screen.
>> >>
>> >> The current architecture seems to be here that the entire view is
>> >> "rendered" on the server irrespective of how much of it is displayed
>> >> in the client. This rules out 1)
>> >>
>> >> Still the current architecture allows to exploit 2) which would solve
>> >> your performance problem if applicable to your use case. But that is
>> >> theory until someone creates TableCellRenderer for Wicket.
>> >>
>> >> Kind Regards,
>> >>
>> >> Bernard
>> >>
>> >> On Tue, 26 Mar 2013 16:07:17 +0100, you wrote:
>> >> >Hi,
>> >> >
>> >> >Lets say I have about ~100.000 of MarkupContainer objects that I want to
>> >> >put into a ListView or RepeatingView.
>> >> >This works fine functional wise... It's rather slow though.
>> >> >
>> >> >It boils down to:
>> >> >MarkupContainer:
>> >> >1309 private Component put(final Component child)
>> >> >1310 {
>> >> >1311 int index = children_indexOf(child);
>> >> >1312 if (index == -1)
>> >> >1313 {
>> >> >1314 children_add(child);
>> >> >1315 return null;
>> >> >1316 }
>> >> >1317 else
>> >> >1318 {
>> >> >1319 return children_set(index, child);
>> >> >1320 }
>> >> >1321 }
>> >> >
>> >> >and the call to "children_indexOf(child)" where it loops over all it's
>> >> >existing children and compares the id's until a match is found.
>> >> >With an increasing amount of children this can get rather slow...
>> >> >
>> >> >I though off overruling some functionality in the MarkupContainer class
>> >> >since I'm sure that for this list of items the children will be unique
>> >> >in
>> >> >their id and don't need that lookup, and overruling the "put" or
>> >> >"children_indexOf" function would give me enough power to skip that
>> >> >performance impacting part. But most functions have private access,
>> >> >leaving me nothing to control the adding of child components to a
>> >> >MarkupContainer.
>> >> >
>> >> >Does anyone else have experience with adding rather large quantities to
>> >> >something like the ListView and/or RepeatingView?
>> >> >Or is there another way of rendering this large amount of containers?
>> >> >
>> >> >Thanks in advance.
>> >> >
>> >> >Kind regards,
>> >> >Marco
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Marco Springer <ma...@glitchbox.nl>.
On Tuesday 26 March 2013 13:48:05 Igor Vaynberg wrote:
> On Tue, Mar 26, 2013 at 1:31 PM, Marco Springer <ma...@glitchbox.nl> wrote:
> > Actually, the performance problem was in the first row, well actually the
> > header that was rendering all days in a week/month/year.
> >
> > Each data row itself has a lot less items.
> > Each row has items that are absolutely positioned within the relatively
> > positioned row. Each item can span over multiple days/week/months or even
> > years, depending on the task duration.
> >
> > Doing this instead of rendering divs for each day saves a lot of
> > calculation on the server side and a whole lot less html on the client
> > side.
> > And this creates other nifty possibilities like making the item divs
> > resizable and draggable in that row with bound ajax calls to those
> > actions.
> > For showing a grid I've done some background images that match the zoom
> > level, since each day is static in width.
> >
> > I've thought about lazy loading the rows that where outside of the
> > scrollable view, since I indeed have a scrollable view.
> > But that's something for the future.
> >
> > Rendering the 287 years
>
> pretty sure gantt charts didnt exist 287 years ago... :)
who talks about the past! the future baby! 26 Feb 2013 - 26 Feb 2300 :)
>
> -igor
>
> > , e.g. 104k~ ish days, did render eventually and the server
> > and browser didn't choke, but the div with was about 5M px width wide, so
> > that was nonsense :P
> >
> > On Wednesday 27 March 2013 05:25:40 Bernard wrote:
> >> Hi,
> >>
> >> AFAIK the solutions for large numbers of cells in GUI frameworks are:
> >>
> >> 1) Do not render cells that are not in the scrollable view
> >> 2) Create components only per once row or column and provide cell
> >> renderers. See javax.swing.table.TableCellRenderer
> >>
> >> With these approaches there is basically no limit to the amount of
> >> data that can be displayed on the screen.
> >>
> >> The current architecture seems to be here that the entire view is
> >> "rendered" on the server irrespective of how much of it is displayed
> >> in the client. This rules out 1)
> >>
> >> Still the current architecture allows to exploit 2) which would solve
> >> your performance problem if applicable to your use case. But that is
> >> theory until someone creates TableCellRenderer for Wicket.
> >>
> >> Kind Regards,
> >>
> >> Bernard
> >>
> >> On Tue, 26 Mar 2013 16:07:17 +0100, you wrote:
> >> >Hi,
> >> >
> >> >Lets say I have about ~100.000 of MarkupContainer objects that I want to
> >> >put into a ListView or RepeatingView.
> >> >This works fine functional wise... It's rather slow though.
> >> >
> >> >It boils down to:
> >> >MarkupContainer:
> >> >1309 private Component put(final Component child)
> >> >1310 {
> >> >1311 int index = children_indexOf(child);
> >> >1312 if (index == -1)
> >> >1313 {
> >> >1314 children_add(child);
> >> >1315 return null;
> >> >1316 }
> >> >1317 else
> >> >1318 {
> >> >1319 return children_set(index, child);
> >> >1320 }
> >> >1321 }
> >> >
> >> >and the call to "children_indexOf(child)" where it loops over all it's
> >> >existing children and compares the id's until a match is found.
> >> >With an increasing amount of children this can get rather slow...
> >> >
> >> >I though off overruling some functionality in the MarkupContainer class
> >> >since I'm sure that for this list of items the children will be unique
> >> >in
> >> >their id and don't need that lookup, and overruling the "put" or
> >> >"children_indexOf" function would give me enough power to skip that
> >> >performance impacting part. But most functions have private access,
> >> >leaving me nothing to control the adding of child components to a
> >> >MarkupContainer.
> >> >
> >> >Does anyone else have experience with adding rather large quantities to
> >> >something like the ListView and/or RepeatingView?
> >> >Or is there another way of rendering this large amount of containers?
> >> >
> >> >Thanks in advance.
> >> >
> >> >Kind regards,
> >> >Marco
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Igor Vaynberg <ig...@gmail.com>.
On Tue, Mar 26, 2013 at 1:31 PM, Marco Springer <ma...@glitchbox.nl> wrote:
> Actually, the performance problem was in the first row, well actually the header that
> was rendering all days in a week/month/year.
>
> Each data row itself has a lot less items.
> Each row has items that are absolutely positioned within the relatively positioned row.
> Each item can span over multiple days/week/months or even years, depending on the
> task duration.
>
> Doing this instead of rendering divs for each day saves a lot of calculation on the
> server side and a whole lot less html on the client side.
> And this creates other nifty possibilities like making the item divs resizable and
> draggable in that row with bound ajax calls to those actions.
> For showing a grid I've done some background images that match the zoom level,
> since each day is static in width.
>
> I've thought about lazy loading the rows that where outside of the scrollable view,
> since I indeed have a scrollable view.
> But that's something for the future.
>
> Rendering the 287 years
pretty sure gantt charts didnt exist 287 years ago... :)
-igor
> , e.g. 104k~ ish days, did render eventually and the server
> and browser didn't choke, but the div with was about 5M px width wide, so that was
> nonsense :P
>
> On Wednesday 27 March 2013 05:25:40 Bernard wrote:
>> Hi,
>>
>> AFAIK the solutions for large numbers of cells in GUI frameworks are:
>>
>> 1) Do not render cells that are not in the scrollable view
>> 2) Create components only per once row or column and provide cell
>> renderers. See javax.swing.table.TableCellRenderer
>>
>> With these approaches there is basically no limit to the amount of
>> data that can be displayed on the screen.
>>
>> The current architecture seems to be here that the entire view is
>> "rendered" on the server irrespective of how much of it is displayed
>> in the client. This rules out 1)
>>
>> Still the current architecture allows to exploit 2) which would solve
>> your performance problem if applicable to your use case. But that is
>> theory until someone creates TableCellRenderer for Wicket.
>>
>> Kind Regards,
>>
>> Bernard
>>
>> On Tue, 26 Mar 2013 16:07:17 +0100, you wrote:
>> >Hi,
>> >
>> >Lets say I have about ~100.000 of MarkupContainer objects that I want to
>> >put into a ListView or RepeatingView.
>> >This works fine functional wise... It's rather slow though.
>> >
>> >It boils down to:
>> >MarkupContainer:
>> >1309 private Component put(final Component child)
>> >1310 {
>> >1311 int index = children_indexOf(child);
>> >1312 if (index == -1)
>> >1313 {
>> >1314 children_add(child);
>> >1315 return null;
>> >1316 }
>> >1317 else
>> >1318 {
>> >1319 return children_set(index, child);
>> >1320 }
>> >1321 }
>> >
>> >and the call to "children_indexOf(child)" where it loops over all it's
>> >existing children and compares the id's until a match is found.
>> >With an increasing amount of children this can get rather slow...
>> >
>> >I though off overruling some functionality in the MarkupContainer class
>> >since I'm sure that for this list of items the children will be unique in
>> >their id and don't need that lookup, and overruling the "put" or
>> >"children_indexOf" function would give me enough power to skip that
>> >performance impacting part. But most functions have private access,
>> >leaving me nothing to control the adding of child components to a
>> >MarkupContainer.
>> >
>> >Does anyone else have experience with adding rather large quantities to
>> >something like the ListView and/or RepeatingView?
>> >Or is there another way of rendering this large amount of containers?
>> >
>> >Thanks in advance.
>> >
>> >Kind regards,
>> >Marco
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Marco Springer <ma...@glitchbox.nl>.
Actually, the performance problem was in the first row, well actually the header that
was rendering all days in a week/month/year.
Each data row itself has a lot less items.
Each row has items that are absolutely positioned within the relatively positioned row.
Each item can span over multiple days/week/months or even years, depending on the
task duration.
Doing this instead of rendering divs for each day saves a lot of calculation on the
server side and a whole lot less html on the client side.
And this creates other nifty possibilities like making the item divs resizable and
draggable in that row with bound ajax calls to those actions.
For showing a grid I've done some background images that match the zoom level,
since each day is static in width.
I've thought about lazy loading the rows that where outside of the scrollable view,
since I indeed have a scrollable view.
But that's something for the future.
Rendering the 287 years, e.g. 104k~ ish days, did render eventually and the server
and browser didn't choke, but the div with was about 5M px width wide, so that was
nonsense :P
On Wednesday 27 March 2013 05:25:40 Bernard wrote:
> Hi,
>
> AFAIK the solutions for large numbers of cells in GUI frameworks are:
>
> 1) Do not render cells that are not in the scrollable view
> 2) Create components only per once row or column and provide cell
> renderers. See javax.swing.table.TableCellRenderer
>
> With these approaches there is basically no limit to the amount of
> data that can be displayed on the screen.
>
> The current architecture seems to be here that the entire view is
> "rendered" on the server irrespective of how much of it is displayed
> in the client. This rules out 1)
>
> Still the current architecture allows to exploit 2) which would solve
> your performance problem if applicable to your use case. But that is
> theory until someone creates TableCellRenderer for Wicket.
>
> Kind Regards,
>
> Bernard
>
> On Tue, 26 Mar 2013 16:07:17 +0100, you wrote:
> >Hi,
> >
> >Lets say I have about ~100.000 of MarkupContainer objects that I want to
> >put into a ListView or RepeatingView.
> >This works fine functional wise... It's rather slow though.
> >
> >It boils down to:
> >MarkupContainer:
> >1309 private Component put(final Component child)
> >1310 {
> >1311 int index = children_indexOf(child);
> >1312 if (index == -1)
> >1313 {
> >1314 children_add(child);
> >1315 return null;
> >1316 }
> >1317 else
> >1318 {
> >1319 return children_set(index, child);
> >1320 }
> >1321 }
> >
> >and the call to "children_indexOf(child)" where it loops over all it's
> >existing children and compares the id's until a match is found.
> >With an increasing amount of children this can get rather slow...
> >
> >I though off overruling some functionality in the MarkupContainer class
> >since I'm sure that for this list of items the children will be unique in
> >their id and don't need that lookup, and overruling the "put" or
> >"children_indexOf" function would give me enough power to skip that
> >performance impacting part. But most functions have private access,
> >leaving me nothing to control the adding of child components to a
> >MarkupContainer.
> >
> >Does anyone else have experience with adding rather large quantities to
> >something like the ListView and/or RepeatingView?
> >Or is there another way of rendering this large amount of containers?
> >
> >Thanks in advance.
> >
> >Kind regards,
> >Marco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or
RepeatingView
Posted by Bernard <bh...@gmail.com>.
Hi,
AFAIK the solutions for large numbers of cells in GUI frameworks are:
1) Do not render cells that are not in the scrollable view
2) Create components only per once row or column and provide cell
renderers. See javax.swing.table.TableCellRenderer
With these approaches there is basically no limit to the amount of
data that can be displayed on the screen.
The current architecture seems to be here that the entire view is
"rendered" on the server irrespective of how much of it is displayed
in the client. This rules out 1)
Still the current architecture allows to exploit 2) which would solve
your performance problem if applicable to your use case. But that is
theory until someone creates TableCellRenderer for Wicket.
Kind Regards,
Bernard
On Tue, 26 Mar 2013 16:07:17 +0100, you wrote:
>Hi,
>
>Lets say I have about ~100.000 of MarkupContainer objects that I want to put
>into a ListView or RepeatingView.
>This works fine functional wise... It's rather slow though.
>
>It boils down to:
>MarkupContainer:
>1309 private Component put(final Component child)
>1310 {
>1311 int index = children_indexOf(child);
>1312 if (index == -1)
>1313 {
>1314 children_add(child);
>1315 return null;
>1316 }
>1317 else
>1318 {
>1319 return children_set(index, child);
>1320 }
>1321 }
>
>and the call to "children_indexOf(child)" where it loops over all it's
>existing children and compares the id's until a match is found.
>With an increasing amount of children this can get rather slow...
>
>I though off overruling some functionality in the MarkupContainer class since
>I'm sure that for this list of items the children will be unique in their id
>and don't need that lookup, and overruling the "put" or "children_indexOf"
>function would give me enough power to skip that performance impacting part.
>But most functions have private access, leaving me nothing to control the
>adding of child components to a MarkupContainer.
>
>Does anyone else have experience with adding rather large quantities to
>something like the ListView and/or RepeatingView?
>Or is there another way of rendering this large amount of containers?
>
>Thanks in advance.
>
>Kind regards,
>Marco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Martin Grigorov <mg...@apache.org>.
Even if you overcome this slowness in Wicket code - how do you imagine the
browser will render such amount of markup ?
Even 500 HTML elements (e.g. table rows) will make it hard for the browser
to render them.
On Tue, Mar 26, 2013 at 5:07 PM, Marco Springer <ma...@glitchbox.nl> wrote:
> Hi,
>
> Lets say I have about ~100.000 of MarkupContainer objects that I want to
> put
> into a ListView or RepeatingView.
> This works fine functional wise... It's rather slow though.
>
> It boils down to:
> MarkupContainer:
> 1309 private Component put(final Component child)
> 1310 {
> 1311 int index = children_indexOf(child);
> 1312 if (index == -1)
> 1313 {
> 1314 children_add(child);
> 1315 return null;
> 1316 }
> 1317 else
> 1318 {
> 1319 return children_set(index, child);
> 1320 }
> 1321 }
>
> and the call to "children_indexOf(child)" where it loops over all it's
> existing children and compares the id's until a match is found.
> With an increasing amount of children this can get rather slow...
>
> I though off overruling some functionality in the MarkupContainer class
> since
> I'm sure that for this list of items the children will be unique in their
> id
> and don't need that lookup, and overruling the "put" or "children_indexOf"
> function would give me enough power to skip that performance impacting
> part.
> But most functions have private access, leaving me nothing to control the
> adding of child components to a MarkupContainer.
>
> Does anyone else have experience with adding rather large quantities to
> something like the ListView and/or RepeatingView?
> Or is there another way of rendering this large amount of containers?
>
> Thanks in advance.
>
> Kind regards,
> Marco
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Marco Springer <ma...@glitchbox.nl>.
Hi Dan,
Tnx for the suggestion.
In the previous mail I mentioned to present a zoomed out version of the Gantt
which is a logical view considering the display of several years, the detail
of showing each day in those years is, well, useless.
It was easy to change this, therefor not needing the sublisting and no
architecture overhaul :).
Again, I agree on keeping a lid on the amount of rendered components. Which I
managed to do.
On Tuesday 26 March 2013 10:52:53 Dan Retzlaff wrote:
> The javadoc for Component#put() refers to a now non-existent "childForId
> map" which got removed 8 years ago [1]!
>
> You might consider making your ListView<T> into a ListView<List<T>> and
> splitting the original dataset into say 10k List#subLists. It ain't pretty,
> but for a "(nearly finished)" app, it beats a serious architecture overhaul
> or waiting for a dubious change to wicket-core. Throw in some
> item.setRenderBodyOnly(true) and your markup will be none the wiser. :)
>
> [1]
> https://github.com/apache/wicket/commit/0a321ea04887a3113e183b46ab20c1c5d702
> 2de0#wicket/src/java/wicket/MarkupContainer.java
> On Tue, Mar 26, 2013 at 9:23 AM, Marco Springer <ma...@glitchbox.nl> wrote:
> > I'm building a Gantt like interface with Wicket (nearly finished).
> > It was a requirement to see multiple years of planned items, in the
> > extreme
> > range even.
> >
> > I've down-tuned it to be around max ~3k (8 years) of components in that
> > listview, through the power of persuasion and as a test.
> > At 3k components, the getId() method is called quite a reasonable amount
> > of
> > times. around 4.5M'ish times through the children_indexOf method.
> >
> > But you're absolutely right, 100k components is bull.
> >
> > Right now I've settled with them that I'd change the view of the Gantt to
> > be
> > less detailed when that amount of data is in there. The UI is quite
> > flexible in
> > that I can change what I render.
> >
> > With 2 years, only 731 columns are rendered, each day is a column.
> > When > 2 years, I change the view to a more zoomed out version.
> > With 8 years, only 97 columns are rendered, each month being a column.
> >
> > Etc...
> >
> > Still with all the components taken in as it is a Gantt chart kinda
> > interface,
> > the browsers that I test in are only getting a bit sluggish when I'm
> > displaying around 2k of components on this Intel Q8200.
> > I'm not displaying any fancy gif's/flash or whatever, only allot of div's
> > and
> > some svg overlays through jsPlumb for dependency display.
> >
> > I mainly found it staggering that the getId() function was called that
> > much.
> > As Martin said, I'm targeting to limit the amount of components that
> > should be
> > rendered now, although sometimes hard with this kind of interface.
> >
> > Cheers.
> >
> > On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > > putting a 100000 components into a page is ill advised even if they
> > > are under different parents.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Paul Bors <pa...@bors.ws>.
Get rid of your large scroll area and use data tables with 50-100 rows per
page along with a filter panel.
That'll be more like the "wicket developer" way.
As for the fancy infinite scrolling, I would strongly suggest you take the
advise and consider what Martin said about using lazy loading repeaters
with DOM elements being added and removed unless you want to get the all
familiar "This application stopped responding, would you like to terminate
it now" error from Windows whenever you scroll past first few hundred rows
in IE :)
~ Thank you,
Paul Bors
On Wed, Mar 27, 2013 at 9:29 AM, vineet semwal <vi...@gmail.com>wrote:
> i was expecting this case too :-) but it's a very unusual usecase for a
> *user* but not for wicket developer ,i have an easy(may be stupid) idea for
> this,no need of quickview :-) ,show only one repeater's page items to user
> like as usual.., on scroll event just repaint the repeater's parent
> ,foreg. with dataview on event
>
> dataview.setcurrentpage(dataview.getcurrentpage()+1) //plus or minus 1
> depending on scroll direction
> target.add(parent)
>
> that might be the cheapest/baddest way of achieving this usecase :-)
>
>
> On Wed, Mar 27, 2013 at 5:28 PM, Martin Grigorov <mgrigorov@apache.org
> >wrote:
>
> > Hi,
> >
> > I mean something like
> > https://github.com/mleibman/SlickGrid/wiki#virtual-rendering - DOM
> objects
> > are added and removed while scrolling, thus keeping the DOM tree size
> small
> >
> >
> > On Wed, Mar 27, 2013 at 12:52 PM, vineet semwal <
> vineetsemwal82@gmail.com
> > >wrote:
> >
> > > hi ,
> > > do you mean removing items when you said unloading?
> > > the scroll behavior and navigator that are in the package just do
> > > quickview#addItemsForNextPage() on event like in this example
> > >
> > >
> >
> https://github.com/vineetsemwal/quickview/blob/master/wicket-quickview-examples/src/main/java/com/aplombee/examples/PageScrollBar.java
> > >
> > > somone who doesn't want to maintain state can do
> > >
> > > *protected* void onScroll(AjaxRequestTarget target) {
> > > //this removes items but do not update client view
> > > quickView.simpleRemoveAll();
> > > addItemsForNextPage(quickView);
> > > }
> > >
> > > as in this case the state is not maintained hence not good for someone
> > > who wants to use stateful components ..
> > > may be i am just misunderstanding you :-)
> > >
> > >
> > >
> > > On Wed, Mar 27, 2013 at 1:01 PM, Martin Grigorov <mgrigorov@apache.org
> > > >wrote:
> > >
> > > > Check https://github.com/vineetsemwal/quickview - a lazy loading
> > > repeater.
> > > > I'm not sure whether it also unloads items which are no more visible.
> > > >
> > > >
> > > > On Wed, Mar 27, 2013 at 12:16 AM, Ernesto Reinaldo Barreiro <
> > > > reiern70@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Angular is just a "detail" on the approach I was suggesting... You
> > can
> > > > > achieve "the same" using "plain" jquery to ask for JSON and do
> > > "creation"
> > > > > of rows at client side iterating over results. If you do thing
> nicely
> > > you
> > > > > can still have some kind of componentization and the performance
> will
> > > be
> > > > a
> > > > > lot better... Not to mention use of resources at server side.
> > > > >
> > > > > On Tue, Mar 26, 2013 at 9:10 PM, Marco Springer <
> marco@glitchbox.nl>
> > > > > wrote:
> > > > >
> > > > > > I've looked at Angular a while back and it certainly looks
> > > interesting.
> > > > > >
> > > > > > However I don't think it's wise to introduce another technology
> > > within
> > > > > the
> > > > > > current company where I'm migrating a rather large CGI-BIN
> > > application
> > > > > to a
> > > > > > Wicket variant and into several modules.
> > > > > > I'm the main JAVA/Wicket guy now, the others are mainly C++
> > > developers
> > > > > with
> > > > > > some JAVA knowledge and growing in that knowledge as more and
> more
> > > > parts
> > > > > > are
> > > > > > converted into Wicket counterparts.
> > > > > > So they already have to get known with:
> > > > > > Hibernate, parts of Spring, Wicket, Maven and HTML, CSS & JS.
> > > > > >
> > > > > > Sooo for now.. I'm sticking with Wicket only.
> > > > > > And with the zoomed out version and restricting the date range,
> > ergo
> > > > > > reducing
> > > > > > the amount of components.., that fixes things.
> > > > > >
> > > > > > The future will give me plenty of time make things even fancier.
> > > > Perhaps
> > > > > > even
> > > > > > the use of Angular.
> > > > > >
> > > > > > On Tuesday 26 March 2013 19:55:30 Ernesto Reinaldo Barreiro
> wrote:
> > > > > > > I mean: This same component could be used as "context" for AJAX
> > > > > > > interactions.
> > > > > > >
> > > > > > > On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
> > > > > > >
> > > > > > > reiern70@gmail.com> wrote:
> > > > > > > > Why don't you try rolling your own component that at sever
> side
> > > > just
> > > > > > > > serves JSON and you build up "rich functionality" at client
> > side.
> > > > > This
> > > > > > > > same
> > > > > > > > context could be used as "context" for AJAX interactions.
> > > Something
> > > > > > like
> > > > > > > >
> > > > > > > > http://www.antiliasoft.com/wicket-angular-demo/
> > > > > > > >
> > > > > > > > On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <
> > > > marco@glitchbox.nl
> > > > > > >wrote:
> > > > > > > >> I'm building a Gantt like interface with Wicket (nearly
> > > finished).
> > > > > > > >> It was a requirement to see multiple years of planned items,
> > in
> > > > the
> > > > > > > >> extreme
> > > > > > > >> range even.
> > > > > > > >>
> > > > > > > >> I've down-tuned it to be around max ~3k (8 years) of
> > components
> > > in
> > > > > > that
> > > > > > > >> listview, through the power of persuasion and as a test.
> > > > > > > >> At 3k components, the getId() method is called quite a
> > > reasonable
> > > > > > amount
> > > > > > > >> of
> > > > > > > >> times. around 4.5M'ish times through the children_indexOf
> > > method.
> > > > > > > >>
> > > > > > > >> But you're absolutely right, 100k components is bull.
> > > > > > > >>
> > > > > > > >> Right now I've settled with them that I'd change the view of
> > the
> > > > > > Gantt to
> > > > > > > >> be
> > > > > > > >> less detailed when that amount of data is in there. The UI
> is
> > > > quite
> > > > > > > >> flexible in
> > > > > > > >> that I can change what I render.
> > > > > > > >>
> > > > > > > >> With 2 years, only 731 columns are rendered, each day is a
> > > column.
> > > > > > > >> When > 2 years, I change the view to a more zoomed out
> > version.
> > > > > > > >> With 8 years, only 97 columns are rendered, each month
> being a
> > > > > column.
> > > > > > > >>
> > > > > > > >> Etc...
> > > > > > > >>
> > > > > > > >> Still with all the components taken in as it is a Gantt
> chart
> > > > kinda
> > > > > > > >> interface,
> > > > > > > >> the browsers that I test in are only getting a bit sluggish
> > when
> > > > I'm
> > > > > > > >> displaying around 2k of components on this Intel Q8200.
> > > > > > > >> I'm not displaying any fancy gif's/flash or whatever, only
> > allot
> > > > of
> > > > > > div's
> > > > > > > >> and
> > > > > > > >> some svg overlays through jsPlumb for dependency display.
> > > > > > > >>
> > > > > > > >> I mainly found it staggering that the getId() function was
> > > called
> > > > > that
> > > > > > > >> much.
> > > > > > > >> As Martin said, I'm targeting to limit the amount of
> > components
> > > > that
> > > > > > > >> should be
> > > > > > > >> rendered now, although sometimes hard with this kind of
> > > interface.
> > > > > > > >>
> > > > > > > >> Cheers.
> > > > > > > >>
> > > > > > > >> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > > > > > > >> > putting a 100000 components into a page is ill advised
> even
> > if
> > > > > they
> > > > > > > >> > are under different parents.
> > > > > > > >>
> > > > > > > >>
> > > > >
> ---------------------------------------------------------------------
> > > > > > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > >> For additional commands, e-mail:
> users-help@wicket.apache.org
> > > > > > > >
> > > > > > > > --
> > > > > > > > Regards - Ernesto Reinaldo Barreiro
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Regards - Ernesto Reinaldo Barreiro
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Martin Grigorov
> > > > jWeekend
> > > > Training, Consulting, Development
> > > > http://jWeekend.com <http://jweekend.com/>
> > > >
> > >
> > >
> > >
> > > --
> > > regards,
> > >
> > > Vineet Semwal
> > >
> >
> >
> >
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com <http://jweekend.com/>
> >
>
>
>
> --
> regards,
>
> Vineet Semwal
>
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by vineet semwal <vi...@gmail.com>.
i was expecting this case too :-) but it's a very unusual usecase for a
*user* but not for wicket developer ,i have an easy(may be stupid) idea for
this,no need of quickview :-) ,show only one repeater's page items to user
like as usual.., on scroll event just repaint the repeater's parent
,foreg. with dataview on event
dataview.setcurrentpage(dataview.getcurrentpage()+1) //plus or minus 1
depending on scroll direction
target.add(parent)
that might be the cheapest/baddest way of achieving this usecase :-)
On Wed, Mar 27, 2013 at 5:28 PM, Martin Grigorov <mg...@apache.org>wrote:
> Hi,
>
> I mean something like
> https://github.com/mleibman/SlickGrid/wiki#virtual-rendering - DOM objects
> are added and removed while scrolling, thus keeping the DOM tree size small
>
>
> On Wed, Mar 27, 2013 at 12:52 PM, vineet semwal <vineetsemwal82@gmail.com
> >wrote:
>
> > hi ,
> > do you mean removing items when you said unloading?
> > the scroll behavior and navigator that are in the package just do
> > quickview#addItemsForNextPage() on event like in this example
> >
> >
> https://github.com/vineetsemwal/quickview/blob/master/wicket-quickview-examples/src/main/java/com/aplombee/examples/PageScrollBar.java
> >
> > somone who doesn't want to maintain state can do
> >
> > *protected* void onScroll(AjaxRequestTarget target) {
> > //this removes items but do not update client view
> > quickView.simpleRemoveAll();
> > addItemsForNextPage(quickView);
> > }
> >
> > as in this case the state is not maintained hence not good for someone
> > who wants to use stateful components ..
> > may be i am just misunderstanding you :-)
> >
> >
> >
> > On Wed, Mar 27, 2013 at 1:01 PM, Martin Grigorov <mgrigorov@apache.org
> > >wrote:
> >
> > > Check https://github.com/vineetsemwal/quickview - a lazy loading
> > repeater.
> > > I'm not sure whether it also unloads items which are no more visible.
> > >
> > >
> > > On Wed, Mar 27, 2013 at 12:16 AM, Ernesto Reinaldo Barreiro <
> > > reiern70@gmail.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > Angular is just a "detail" on the approach I was suggesting... You
> can
> > > > achieve "the same" using "plain" jquery to ask for JSON and do
> > "creation"
> > > > of rows at client side iterating over results. If you do thing nicely
> > you
> > > > can still have some kind of componentization and the performance will
> > be
> > > a
> > > > lot better... Not to mention use of resources at server side.
> > > >
> > > > On Tue, Mar 26, 2013 at 9:10 PM, Marco Springer <ma...@glitchbox.nl>
> > > > wrote:
> > > >
> > > > > I've looked at Angular a while back and it certainly looks
> > interesting.
> > > > >
> > > > > However I don't think it's wise to introduce another technology
> > within
> > > > the
> > > > > current company where I'm migrating a rather large CGI-BIN
> > application
> > > > to a
> > > > > Wicket variant and into several modules.
> > > > > I'm the main JAVA/Wicket guy now, the others are mainly C++
> > developers
> > > > with
> > > > > some JAVA knowledge and growing in that knowledge as more and more
> > > parts
> > > > > are
> > > > > converted into Wicket counterparts.
> > > > > So they already have to get known with:
> > > > > Hibernate, parts of Spring, Wicket, Maven and HTML, CSS & JS.
> > > > >
> > > > > Sooo for now.. I'm sticking with Wicket only.
> > > > > And with the zoomed out version and restricting the date range,
> ergo
> > > > > reducing
> > > > > the amount of components.., that fixes things.
> > > > >
> > > > > The future will give me plenty of time make things even fancier.
> > > Perhaps
> > > > > even
> > > > > the use of Angular.
> > > > >
> > > > > On Tuesday 26 March 2013 19:55:30 Ernesto Reinaldo Barreiro wrote:
> > > > > > I mean: This same component could be used as "context" for AJAX
> > > > > > interactions.
> > > > > >
> > > > > > On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
> > > > > >
> > > > > > reiern70@gmail.com> wrote:
> > > > > > > Why don't you try rolling your own component that at sever side
> > > just
> > > > > > > serves JSON and you build up "rich functionality" at client
> side.
> > > > This
> > > > > > > same
> > > > > > > context could be used as "context" for AJAX interactions.
> > Something
> > > > > like
> > > > > > >
> > > > > > > http://www.antiliasoft.com/wicket-angular-demo/
> > > > > > >
> > > > > > > On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <
> > > marco@glitchbox.nl
> > > > > >wrote:
> > > > > > >> I'm building a Gantt like interface with Wicket (nearly
> > finished).
> > > > > > >> It was a requirement to see multiple years of planned items,
> in
> > > the
> > > > > > >> extreme
> > > > > > >> range even.
> > > > > > >>
> > > > > > >> I've down-tuned it to be around max ~3k (8 years) of
> components
> > in
> > > > > that
> > > > > > >> listview, through the power of persuasion and as a test.
> > > > > > >> At 3k components, the getId() method is called quite a
> > reasonable
> > > > > amount
> > > > > > >> of
> > > > > > >> times. around 4.5M'ish times through the children_indexOf
> > method.
> > > > > > >>
> > > > > > >> But you're absolutely right, 100k components is bull.
> > > > > > >>
> > > > > > >> Right now I've settled with them that I'd change the view of
> the
> > > > > Gantt to
> > > > > > >> be
> > > > > > >> less detailed when that amount of data is in there. The UI is
> > > quite
> > > > > > >> flexible in
> > > > > > >> that I can change what I render.
> > > > > > >>
> > > > > > >> With 2 years, only 731 columns are rendered, each day is a
> > column.
> > > > > > >> When > 2 years, I change the view to a more zoomed out
> version.
> > > > > > >> With 8 years, only 97 columns are rendered, each month being a
> > > > column.
> > > > > > >>
> > > > > > >> Etc...
> > > > > > >>
> > > > > > >> Still with all the components taken in as it is a Gantt chart
> > > kinda
> > > > > > >> interface,
> > > > > > >> the browsers that I test in are only getting a bit sluggish
> when
> > > I'm
> > > > > > >> displaying around 2k of components on this Intel Q8200.
> > > > > > >> I'm not displaying any fancy gif's/flash or whatever, only
> allot
> > > of
> > > > > div's
> > > > > > >> and
> > > > > > >> some svg overlays through jsPlumb for dependency display.
> > > > > > >>
> > > > > > >> I mainly found it staggering that the getId() function was
> > called
> > > > that
> > > > > > >> much.
> > > > > > >> As Martin said, I'm targeting to limit the amount of
> components
> > > that
> > > > > > >> should be
> > > > > > >> rendered now, although sometimes hard with this kind of
> > interface.
> > > > > > >>
> > > > > > >> Cheers.
> > > > > > >>
> > > > > > >> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > > > > > >> > putting a 100000 components into a page is ill advised even
> if
> > > > they
> > > > > > >> > are under different parents.
> > > > > > >>
> > > > > > >>
> > > > ---------------------------------------------------------------------
> > > > > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > >
> > > > > > > --
> > > > > > > Regards - Ernesto Reinaldo Barreiro
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Regards - Ernesto Reinaldo Barreiro
> > > >
> > >
> > >
> > >
> > > --
> > > Martin Grigorov
> > > jWeekend
> > > Training, Consulting, Development
> > > http://jWeekend.com <http://jweekend.com/>
> > >
> >
> >
> >
> > --
> > regards,
> >
> > Vineet Semwal
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com <http://jweekend.com/>
>
--
regards,
Vineet Semwal
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
I mean something like
https://github.com/mleibman/SlickGrid/wiki#virtual-rendering - DOM objects
are added and removed while scrolling, thus keeping the DOM tree size small
On Wed, Mar 27, 2013 at 12:52 PM, vineet semwal <vi...@gmail.com>wrote:
> hi ,
> do you mean removing items when you said unloading?
> the scroll behavior and navigator that are in the package just do
> quickview#addItemsForNextPage() on event like in this example
>
> https://github.com/vineetsemwal/quickview/blob/master/wicket-quickview-examples/src/main/java/com/aplombee/examples/PageScrollBar.java
>
> somone who doesn't want to maintain state can do
>
> *protected* void onScroll(AjaxRequestTarget target) {
> //this removes items but do not update client view
> quickView.simpleRemoveAll();
> addItemsForNextPage(quickView);
> }
>
> as in this case the state is not maintained hence not good for someone
> who wants to use stateful components ..
> may be i am just misunderstanding you :-)
>
>
>
> On Wed, Mar 27, 2013 at 1:01 PM, Martin Grigorov <mgrigorov@apache.org
> >wrote:
>
> > Check https://github.com/vineetsemwal/quickview - a lazy loading
> repeater.
> > I'm not sure whether it also unloads items which are no more visible.
> >
> >
> > On Wed, Mar 27, 2013 at 12:16 AM, Ernesto Reinaldo Barreiro <
> > reiern70@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Angular is just a "detail" on the approach I was suggesting... You can
> > > achieve "the same" using "plain" jquery to ask for JSON and do
> "creation"
> > > of rows at client side iterating over results. If you do thing nicely
> you
> > > can still have some kind of componentization and the performance will
> be
> > a
> > > lot better... Not to mention use of resources at server side.
> > >
> > > On Tue, Mar 26, 2013 at 9:10 PM, Marco Springer <ma...@glitchbox.nl>
> > > wrote:
> > >
> > > > I've looked at Angular a while back and it certainly looks
> interesting.
> > > >
> > > > However I don't think it's wise to introduce another technology
> within
> > > the
> > > > current company where I'm migrating a rather large CGI-BIN
> application
> > > to a
> > > > Wicket variant and into several modules.
> > > > I'm the main JAVA/Wicket guy now, the others are mainly C++
> developers
> > > with
> > > > some JAVA knowledge and growing in that knowledge as more and more
> > parts
> > > > are
> > > > converted into Wicket counterparts.
> > > > So they already have to get known with:
> > > > Hibernate, parts of Spring, Wicket, Maven and HTML, CSS & JS.
> > > >
> > > > Sooo for now.. I'm sticking with Wicket only.
> > > > And with the zoomed out version and restricting the date range, ergo
> > > > reducing
> > > > the amount of components.., that fixes things.
> > > >
> > > > The future will give me plenty of time make things even fancier.
> > Perhaps
> > > > even
> > > > the use of Angular.
> > > >
> > > > On Tuesday 26 March 2013 19:55:30 Ernesto Reinaldo Barreiro wrote:
> > > > > I mean: This same component could be used as "context" for AJAX
> > > > > interactions.
> > > > >
> > > > > On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
> > > > >
> > > > > reiern70@gmail.com> wrote:
> > > > > > Why don't you try rolling your own component that at sever side
> > just
> > > > > > serves JSON and you build up "rich functionality" at client side.
> > > This
> > > > > > same
> > > > > > context could be used as "context" for AJAX interactions.
> Something
> > > > like
> > > > > >
> > > > > > http://www.antiliasoft.com/wicket-angular-demo/
> > > > > >
> > > > > > On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <
> > marco@glitchbox.nl
> > > > >wrote:
> > > > > >> I'm building a Gantt like interface with Wicket (nearly
> finished).
> > > > > >> It was a requirement to see multiple years of planned items, in
> > the
> > > > > >> extreme
> > > > > >> range even.
> > > > > >>
> > > > > >> I've down-tuned it to be around max ~3k (8 years) of components
> in
> > > > that
> > > > > >> listview, through the power of persuasion and as a test.
> > > > > >> At 3k components, the getId() method is called quite a
> reasonable
> > > > amount
> > > > > >> of
> > > > > >> times. around 4.5M'ish times through the children_indexOf
> method.
> > > > > >>
> > > > > >> But you're absolutely right, 100k components is bull.
> > > > > >>
> > > > > >> Right now I've settled with them that I'd change the view of the
> > > > Gantt to
> > > > > >> be
> > > > > >> less detailed when that amount of data is in there. The UI is
> > quite
> > > > > >> flexible in
> > > > > >> that I can change what I render.
> > > > > >>
> > > > > >> With 2 years, only 731 columns are rendered, each day is a
> column.
> > > > > >> When > 2 years, I change the view to a more zoomed out version.
> > > > > >> With 8 years, only 97 columns are rendered, each month being a
> > > column.
> > > > > >>
> > > > > >> Etc...
> > > > > >>
> > > > > >> Still with all the components taken in as it is a Gantt chart
> > kinda
> > > > > >> interface,
> > > > > >> the browsers that I test in are only getting a bit sluggish when
> > I'm
> > > > > >> displaying around 2k of components on this Intel Q8200.
> > > > > >> I'm not displaying any fancy gif's/flash or whatever, only allot
> > of
> > > > div's
> > > > > >> and
> > > > > >> some svg overlays through jsPlumb for dependency display.
> > > > > >>
> > > > > >> I mainly found it staggering that the getId() function was
> called
> > > that
> > > > > >> much.
> > > > > >> As Martin said, I'm targeting to limit the amount of components
> > that
> > > > > >> should be
> > > > > >> rendered now, although sometimes hard with this kind of
> interface.
> > > > > >>
> > > > > >> Cheers.
> > > > > >>
> > > > > >> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > > > > >> > putting a 100000 components into a page is ill advised even if
> > > they
> > > > > >> > are under different parents.
> > > > > >>
> > > > > >>
> > > ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > > --
> > > > > > Regards - Ernesto Reinaldo Barreiro
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Regards - Ernesto Reinaldo Barreiro
> > >
> >
> >
> >
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com <http://jweekend.com/>
> >
>
>
>
> --
> regards,
>
> Vineet Semwal
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by vineet semwal <vi...@gmail.com>.
hi ,
do you mean removing items when you said unloading?
the scroll behavior and navigator that are in the package just do
quickview#addItemsForNextPage() on event like in this example
https://github.com/vineetsemwal/quickview/blob/master/wicket-quickview-examples/src/main/java/com/aplombee/examples/PageScrollBar.java
somone who doesn't want to maintain state can do
*protected* void onScroll(AjaxRequestTarget target) {
//this removes items but do not update client view
quickView.simpleRemoveAll();
addItemsForNextPage(quickView);
}
as in this case the state is not maintained hence not good for someone
who wants to use stateful components ..
may be i am just misunderstanding you :-)
On Wed, Mar 27, 2013 at 1:01 PM, Martin Grigorov <mg...@apache.org>wrote:
> Check https://github.com/vineetsemwal/quickview - a lazy loading repeater.
> I'm not sure whether it also unloads items which are no more visible.
>
>
> On Wed, Mar 27, 2013 at 12:16 AM, Ernesto Reinaldo Barreiro <
> reiern70@gmail.com> wrote:
>
> > Hi,
> >
> > Angular is just a "detail" on the approach I was suggesting... You can
> > achieve "the same" using "plain" jquery to ask for JSON and do "creation"
> > of rows at client side iterating over results. If you do thing nicely you
> > can still have some kind of componentization and the performance will be
> a
> > lot better... Not to mention use of resources at server side.
> >
> > On Tue, Mar 26, 2013 at 9:10 PM, Marco Springer <ma...@glitchbox.nl>
> > wrote:
> >
> > > I've looked at Angular a while back and it certainly looks interesting.
> > >
> > > However I don't think it's wise to introduce another technology within
> > the
> > > current company where I'm migrating a rather large CGI-BIN application
> > to a
> > > Wicket variant and into several modules.
> > > I'm the main JAVA/Wicket guy now, the others are mainly C++ developers
> > with
> > > some JAVA knowledge and growing in that knowledge as more and more
> parts
> > > are
> > > converted into Wicket counterparts.
> > > So they already have to get known with:
> > > Hibernate, parts of Spring, Wicket, Maven and HTML, CSS & JS.
> > >
> > > Sooo for now.. I'm sticking with Wicket only.
> > > And with the zoomed out version and restricting the date range, ergo
> > > reducing
> > > the amount of components.., that fixes things.
> > >
> > > The future will give me plenty of time make things even fancier.
> Perhaps
> > > even
> > > the use of Angular.
> > >
> > > On Tuesday 26 March 2013 19:55:30 Ernesto Reinaldo Barreiro wrote:
> > > > I mean: This same component could be used as "context" for AJAX
> > > > interactions.
> > > >
> > > > On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
> > > >
> > > > reiern70@gmail.com> wrote:
> > > > > Why don't you try rolling your own component that at sever side
> just
> > > > > serves JSON and you build up "rich functionality" at client side.
> > This
> > > > > same
> > > > > context could be used as "context" for AJAX interactions. Something
> > > like
> > > > >
> > > > > http://www.antiliasoft.com/wicket-angular-demo/
> > > > >
> > > > > On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <
> marco@glitchbox.nl
> > > >wrote:
> > > > >> I'm building a Gantt like interface with Wicket (nearly finished).
> > > > >> It was a requirement to see multiple years of planned items, in
> the
> > > > >> extreme
> > > > >> range even.
> > > > >>
> > > > >> I've down-tuned it to be around max ~3k (8 years) of components in
> > > that
> > > > >> listview, through the power of persuasion and as a test.
> > > > >> At 3k components, the getId() method is called quite a reasonable
> > > amount
> > > > >> of
> > > > >> times. around 4.5M'ish times through the children_indexOf method.
> > > > >>
> > > > >> But you're absolutely right, 100k components is bull.
> > > > >>
> > > > >> Right now I've settled with them that I'd change the view of the
> > > Gantt to
> > > > >> be
> > > > >> less detailed when that amount of data is in there. The UI is
> quite
> > > > >> flexible in
> > > > >> that I can change what I render.
> > > > >>
> > > > >> With 2 years, only 731 columns are rendered, each day is a column.
> > > > >> When > 2 years, I change the view to a more zoomed out version.
> > > > >> With 8 years, only 97 columns are rendered, each month being a
> > column.
> > > > >>
> > > > >> Etc...
> > > > >>
> > > > >> Still with all the components taken in as it is a Gantt chart
> kinda
> > > > >> interface,
> > > > >> the browsers that I test in are only getting a bit sluggish when
> I'm
> > > > >> displaying around 2k of components on this Intel Q8200.
> > > > >> I'm not displaying any fancy gif's/flash or whatever, only allot
> of
> > > div's
> > > > >> and
> > > > >> some svg overlays through jsPlumb for dependency display.
> > > > >>
> > > > >> I mainly found it staggering that the getId() function was called
> > that
> > > > >> much.
> > > > >> As Martin said, I'm targeting to limit the amount of components
> that
> > > > >> should be
> > > > >> rendered now, although sometimes hard with this kind of interface.
> > > > >>
> > > > >> Cheers.
> > > > >>
> > > > >> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > > > >> > putting a 100000 components into a page is ill advised even if
> > they
> > > > >> > are under different parents.
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > > --
> > > > > Regards - Ernesto Reinaldo Barreiro
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com <http://jweekend.com/>
>
--
regards,
Vineet Semwal
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Martin Grigorov <mg...@apache.org>.
Check https://github.com/vineetsemwal/quickview - a lazy loading repeater.
I'm not sure whether it also unloads items which are no more visible.
On Wed, Mar 27, 2013 at 12:16 AM, Ernesto Reinaldo Barreiro <
reiern70@gmail.com> wrote:
> Hi,
>
> Angular is just a "detail" on the approach I was suggesting... You can
> achieve "the same" using "plain" jquery to ask for JSON and do "creation"
> of rows at client side iterating over results. If you do thing nicely you
> can still have some kind of componentization and the performance will be a
> lot better... Not to mention use of resources at server side.
>
> On Tue, Mar 26, 2013 at 9:10 PM, Marco Springer <ma...@glitchbox.nl>
> wrote:
>
> > I've looked at Angular a while back and it certainly looks interesting.
> >
> > However I don't think it's wise to introduce another technology within
> the
> > current company where I'm migrating a rather large CGI-BIN application
> to a
> > Wicket variant and into several modules.
> > I'm the main JAVA/Wicket guy now, the others are mainly C++ developers
> with
> > some JAVA knowledge and growing in that knowledge as more and more parts
> > are
> > converted into Wicket counterparts.
> > So they already have to get known with:
> > Hibernate, parts of Spring, Wicket, Maven and HTML, CSS & JS.
> >
> > Sooo for now.. I'm sticking with Wicket only.
> > And with the zoomed out version and restricting the date range, ergo
> > reducing
> > the amount of components.., that fixes things.
> >
> > The future will give me plenty of time make things even fancier. Perhaps
> > even
> > the use of Angular.
> >
> > On Tuesday 26 March 2013 19:55:30 Ernesto Reinaldo Barreiro wrote:
> > > I mean: This same component could be used as "context" for AJAX
> > > interactions.
> > >
> > > On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
> > >
> > > reiern70@gmail.com> wrote:
> > > > Why don't you try rolling your own component that at sever side just
> > > > serves JSON and you build up "rich functionality" at client side.
> This
> > > > same
> > > > context could be used as "context" for AJAX interactions. Something
> > like
> > > >
> > > > http://www.antiliasoft.com/wicket-angular-demo/
> > > >
> > > > On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <marco@glitchbox.nl
> > >wrote:
> > > >> I'm building a Gantt like interface with Wicket (nearly finished).
> > > >> It was a requirement to see multiple years of planned items, in the
> > > >> extreme
> > > >> range even.
> > > >>
> > > >> I've down-tuned it to be around max ~3k (8 years) of components in
> > that
> > > >> listview, through the power of persuasion and as a test.
> > > >> At 3k components, the getId() method is called quite a reasonable
> > amount
> > > >> of
> > > >> times. around 4.5M'ish times through the children_indexOf method.
> > > >>
> > > >> But you're absolutely right, 100k components is bull.
> > > >>
> > > >> Right now I've settled with them that I'd change the view of the
> > Gantt to
> > > >> be
> > > >> less detailed when that amount of data is in there. The UI is quite
> > > >> flexible in
> > > >> that I can change what I render.
> > > >>
> > > >> With 2 years, only 731 columns are rendered, each day is a column.
> > > >> When > 2 years, I change the view to a more zoomed out version.
> > > >> With 8 years, only 97 columns are rendered, each month being a
> column.
> > > >>
> > > >> Etc...
> > > >>
> > > >> Still with all the components taken in as it is a Gantt chart kinda
> > > >> interface,
> > > >> the browsers that I test in are only getting a bit sluggish when I'm
> > > >> displaying around 2k of components on this Intel Q8200.
> > > >> I'm not displaying any fancy gif's/flash or whatever, only allot of
> > div's
> > > >> and
> > > >> some svg overlays through jsPlumb for dependency display.
> > > >>
> > > >> I mainly found it staggering that the getId() function was called
> that
> > > >> much.
> > > >> As Martin said, I'm targeting to limit the amount of components that
> > > >> should be
> > > >> rendered now, although sometimes hard with this kind of interface.
> > > >>
> > > >> Cheers.
> > > >>
> > > >> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > > >> > putting a 100000 components into a page is ill advised even if
> they
> > > >> > are under different parents.
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > > --
> > > > Regards - Ernesto Reinaldo Barreiro
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi,
Angular is just a "detail" on the approach I was suggesting... You can
achieve "the same" using "plain" jquery to ask for JSON and do "creation"
of rows at client side iterating over results. If you do thing nicely you
can still have some kind of componentization and the performance will be a
lot better... Not to mention use of resources at server side.
On Tue, Mar 26, 2013 at 9:10 PM, Marco Springer <ma...@glitchbox.nl> wrote:
> I've looked at Angular a while back and it certainly looks interesting.
>
> However I don't think it's wise to introduce another technology within the
> current company where I'm migrating a rather large CGI-BIN application to a
> Wicket variant and into several modules.
> I'm the main JAVA/Wicket guy now, the others are mainly C++ developers with
> some JAVA knowledge and growing in that knowledge as more and more parts
> are
> converted into Wicket counterparts.
> So they already have to get known with:
> Hibernate, parts of Spring, Wicket, Maven and HTML, CSS & JS.
>
> Sooo for now.. I'm sticking with Wicket only.
> And with the zoomed out version and restricting the date range, ergo
> reducing
> the amount of components.., that fixes things.
>
> The future will give me plenty of time make things even fancier. Perhaps
> even
> the use of Angular.
>
> On Tuesday 26 March 2013 19:55:30 Ernesto Reinaldo Barreiro wrote:
> > I mean: This same component could be used as "context" for AJAX
> > interactions.
> >
> > On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
> >
> > reiern70@gmail.com> wrote:
> > > Why don't you try rolling your own component that at sever side just
> > > serves JSON and you build up "rich functionality" at client side. This
> > > same
> > > context could be used as "context" for AJAX interactions. Something
> like
> > >
> > > http://www.antiliasoft.com/wicket-angular-demo/
> > >
> > > On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <marco@glitchbox.nl
> >wrote:
> > >> I'm building a Gantt like interface with Wicket (nearly finished).
> > >> It was a requirement to see multiple years of planned items, in the
> > >> extreme
> > >> range even.
> > >>
> > >> I've down-tuned it to be around max ~3k (8 years) of components in
> that
> > >> listview, through the power of persuasion and as a test.
> > >> At 3k components, the getId() method is called quite a reasonable
> amount
> > >> of
> > >> times. around 4.5M'ish times through the children_indexOf method.
> > >>
> > >> But you're absolutely right, 100k components is bull.
> > >>
> > >> Right now I've settled with them that I'd change the view of the
> Gantt to
> > >> be
> > >> less detailed when that amount of data is in there. The UI is quite
> > >> flexible in
> > >> that I can change what I render.
> > >>
> > >> With 2 years, only 731 columns are rendered, each day is a column.
> > >> When > 2 years, I change the view to a more zoomed out version.
> > >> With 8 years, only 97 columns are rendered, each month being a column.
> > >>
> > >> Etc...
> > >>
> > >> Still with all the components taken in as it is a Gantt chart kinda
> > >> interface,
> > >> the browsers that I test in are only getting a bit sluggish when I'm
> > >> displaying around 2k of components on this Intel Q8200.
> > >> I'm not displaying any fancy gif's/flash or whatever, only allot of
> div's
> > >> and
> > >> some svg overlays through jsPlumb for dependency display.
> > >>
> > >> I mainly found it staggering that the getId() function was called that
> > >> much.
> > >> As Martin said, I'm targeting to limit the amount of components that
> > >> should be
> > >> rendered now, although sometimes hard with this kind of interface.
> > >>
> > >> Cheers.
> > >>
> > >> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > >> > putting a 100000 components into a page is ill advised even if they
> > >> > are under different parents.
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >> For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > > --
> > > Regards - Ernesto Reinaldo Barreiro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Marco Springer <ma...@glitchbox.nl>.
I've looked at Angular a while back and it certainly looks interesting.
However I don't think it's wise to introduce another technology within the
current company where I'm migrating a rather large CGI-BIN application to a
Wicket variant and into several modules.
I'm the main JAVA/Wicket guy now, the others are mainly C++ developers with
some JAVA knowledge and growing in that knowledge as more and more parts are
converted into Wicket counterparts.
So they already have to get known with:
Hibernate, parts of Spring, Wicket, Maven and HTML, CSS & JS.
Sooo for now.. I'm sticking with Wicket only.
And with the zoomed out version and restricting the date range, ergo reducing
the amount of components.., that fixes things.
The future will give me plenty of time make things even fancier. Perhaps even
the use of Angular.
On Tuesday 26 March 2013 19:55:30 Ernesto Reinaldo Barreiro wrote:
> I mean: This same component could be used as "context" for AJAX
> interactions.
>
> On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
>
> reiern70@gmail.com> wrote:
> > Why don't you try rolling your own component that at sever side just
> > serves JSON and you build up "rich functionality" at client side. This
> > same
> > context could be used as "context" for AJAX interactions. Something like
> >
> > http://www.antiliasoft.com/wicket-angular-demo/
> >
> > On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <ma...@glitchbox.nl>wrote:
> >> I'm building a Gantt like interface with Wicket (nearly finished).
> >> It was a requirement to see multiple years of planned items, in the
> >> extreme
> >> range even.
> >>
> >> I've down-tuned it to be around max ~3k (8 years) of components in that
> >> listview, through the power of persuasion and as a test.
> >> At 3k components, the getId() method is called quite a reasonable amount
> >> of
> >> times. around 4.5M'ish times through the children_indexOf method.
> >>
> >> But you're absolutely right, 100k components is bull.
> >>
> >> Right now I've settled with them that I'd change the view of the Gantt to
> >> be
> >> less detailed when that amount of data is in there. The UI is quite
> >> flexible in
> >> that I can change what I render.
> >>
> >> With 2 years, only 731 columns are rendered, each day is a column.
> >> When > 2 years, I change the view to a more zoomed out version.
> >> With 8 years, only 97 columns are rendered, each month being a column.
> >>
> >> Etc...
> >>
> >> Still with all the components taken in as it is a Gantt chart kinda
> >> interface,
> >> the browsers that I test in are only getting a bit sluggish when I'm
> >> displaying around 2k of components on this Intel Q8200.
> >> I'm not displaying any fancy gif's/flash or whatever, only allot of div's
> >> and
> >> some svg overlays through jsPlumb for dependency display.
> >>
> >> I mainly found it staggering that the getId() function was called that
> >> much.
> >> As Martin said, I'm targeting to limit the amount of components that
> >> should be
> >> rendered now, although sometimes hard with this kind of interface.
> >>
> >> Cheers.
> >>
> >> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> >> > putting a 100000 components into a page is ill advised even if they
> >> > are under different parents.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
I mean: This same component could be used as "context" for AJAX
interactions.
On Tue, Mar 26, 2013 at 7:42 PM, Ernesto Reinaldo Barreiro <
reiern70@gmail.com> wrote:
> Why don't you try rolling your own component that at sever side just
> serves JSON and you build up "rich functionality" at client side. This same
> context could be used as "context" for AJAX interactions. Something like
>
> http://www.antiliasoft.com/wicket-angular-demo/
>
>
>
> On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <ma...@glitchbox.nl>wrote:
>
>> I'm building a Gantt like interface with Wicket (nearly finished).
>> It was a requirement to see multiple years of planned items, in the
>> extreme
>> range even.
>>
>> I've down-tuned it to be around max ~3k (8 years) of components in that
>> listview, through the power of persuasion and as a test.
>> At 3k components, the getId() method is called quite a reasonable amount
>> of
>> times. around 4.5M'ish times through the children_indexOf method.
>>
>> But you're absolutely right, 100k components is bull.
>>
>> Right now I've settled with them that I'd change the view of the Gantt to
>> be
>> less detailed when that amount of data is in there. The UI is quite
>> flexible in
>> that I can change what I render.
>>
>> With 2 years, only 731 columns are rendered, each day is a column.
>> When > 2 years, I change the view to a more zoomed out version.
>> With 8 years, only 97 columns are rendered, each month being a column.
>>
>> Etc...
>>
>> Still with all the components taken in as it is a Gantt chart kinda
>> interface,
>> the browsers that I test in are only getting a bit sluggish when I'm
>> displaying around 2k of components on this Intel Q8200.
>> I'm not displaying any fancy gif's/flash or whatever, only allot of div's
>> and
>> some svg overlays through jsPlumb for dependency display.
>>
>> I mainly found it staggering that the getId() function was called that
>> much.
>> As Martin said, I'm targeting to limit the amount of components that
>> should be
>> rendered now, although sometimes hard with this kind of interface.
>>
>> Cheers.
>>
>> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
>> > putting a 100000 components into a page is ill advised even if they
>> > are under different parents.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>
--
Regards - Ernesto Reinaldo Barreiro
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Why don't you try rolling your own component that at sever side just serves
JSON and you build up "rich functionality" at client side. This same
context could be used as "context" for AJAX interactions. Something like
http://www.antiliasoft.com/wicket-angular-demo/
On Tue, Mar 26, 2013 at 5:23 PM, Marco Springer <ma...@glitchbox.nl> wrote:
> I'm building a Gantt like interface with Wicket (nearly finished).
> It was a requirement to see multiple years of planned items, in the extreme
> range even.
>
> I've down-tuned it to be around max ~3k (8 years) of components in that
> listview, through the power of persuasion and as a test.
> At 3k components, the getId() method is called quite a reasonable amount of
> times. around 4.5M'ish times through the children_indexOf method.
>
> But you're absolutely right, 100k components is bull.
>
> Right now I've settled with them that I'd change the view of the Gantt to
> be
> less detailed when that amount of data is in there. The UI is quite
> flexible in
> that I can change what I render.
>
> With 2 years, only 731 columns are rendered, each day is a column.
> When > 2 years, I change the view to a more zoomed out version.
> With 8 years, only 97 columns are rendered, each month being a column.
>
> Etc...
>
> Still with all the components taken in as it is a Gantt chart kinda
> interface,
> the browsers that I test in are only getting a bit sluggish when I'm
> displaying around 2k of components on this Intel Q8200.
> I'm not displaying any fancy gif's/flash or whatever, only allot of div's
> and
> some svg overlays through jsPlumb for dependency display.
>
> I mainly found it staggering that the getId() function was called that
> much.
> As Martin said, I'm targeting to limit the amount of components that
> should be
> rendered now, although sometimes hard with this kind of interface.
>
> Cheers.
>
> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > putting a 100000 components into a page is ill advised even if they
> > are under different parents.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Dan Retzlaff <dr...@gmail.com>.
The javadoc for Component#put() refers to a now non-existent "childForId
map" which got removed 8 years ago [1]!
You might consider making your ListView<T> into a ListView<List<T>> and
splitting the original dataset into say 10k List#subLists. It ain't pretty,
but for a "(nearly finished)" app, it beats a serious architecture overhaul
or waiting for a dubious change to wicket-core. Throw in some
item.setRenderBodyOnly(true) and your markup will be none the wiser. :)
[1]
https://github.com/apache/wicket/commit/0a321ea04887a3113e183b46ab20c1c5d7022de0#wicket/src/java/wicket/MarkupContainer.java
On Tue, Mar 26, 2013 at 9:23 AM, Marco Springer <ma...@glitchbox.nl> wrote:
> I'm building a Gantt like interface with Wicket (nearly finished).
> It was a requirement to see multiple years of planned items, in the extreme
> range even.
>
> I've down-tuned it to be around max ~3k (8 years) of components in that
> listview, through the power of persuasion and as a test.
> At 3k components, the getId() method is called quite a reasonable amount of
> times. around 4.5M'ish times through the children_indexOf method.
>
> But you're absolutely right, 100k components is bull.
>
> Right now I've settled with them that I'd change the view of the Gantt to
> be
> less detailed when that amount of data is in there. The UI is quite
> flexible in
> that I can change what I render.
>
> With 2 years, only 731 columns are rendered, each day is a column.
> When > 2 years, I change the view to a more zoomed out version.
> With 8 years, only 97 columns are rendered, each month being a column.
>
> Etc...
>
> Still with all the components taken in as it is a Gantt chart kinda
> interface,
> the browsers that I test in are only getting a bit sluggish when I'm
> displaying around 2k of components on this Intel Q8200.
> I'm not displaying any fancy gif's/flash or whatever, only allot of div's
> and
> some svg overlays through jsPlumb for dependency display.
>
> I mainly found it staggering that the getId() function was called that
> much.
> As Martin said, I'm targeting to limit the amount of components that
> should be
> rendered now, although sometimes hard with this kind of interface.
>
> Cheers.
>
> On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> > putting a 100000 components into a page is ill advised even if they
> > are under different parents.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Marco Springer <ma...@glitchbox.nl>.
I'm building a Gantt like interface with Wicket (nearly finished).
It was a requirement to see multiple years of planned items, in the extreme
range even.
I've down-tuned it to be around max ~3k (8 years) of components in that
listview, through the power of persuasion and as a test.
At 3k components, the getId() method is called quite a reasonable amount of
times. around 4.5M'ish times through the children_indexOf method.
But you're absolutely right, 100k components is bull.
Right now I've settled with them that I'd change the view of the Gantt to be
less detailed when that amount of data is in there. The UI is quite flexible in
that I can change what I render.
With 2 years, only 731 columns are rendered, each day is a column.
When > 2 years, I change the view to a more zoomed out version.
With 8 years, only 97 columns are rendered, each month being a column.
Etc...
Still with all the components taken in as it is a Gantt chart kinda interface,
the browsers that I test in are only getting a bit sluggish when I'm
displaying around 2k of components on this Intel Q8200.
I'm not displaying any fancy gif's/flash or whatever, only allot of div's and
some svg overlays through jsPlumb for dependency display.
I mainly found it staggering that the getId() function was called that much.
As Martin said, I'm targeting to limit the amount of components that should be
rendered now, although sometimes hard with this kind of interface.
Cheers.
On Tuesday 26 March 2013 08:23:19 Igor Vaynberg wrote:
> putting a 100000 components into a page is ill advised even if they
> are under different parents.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Adding a large amount of MarkupContainers into the ListView or RepeatingView
Posted by Igor Vaynberg <ig...@gmail.com>.
putting a 100000 components into a page is ill advised even if they
are under different parents. what is the usecase you are trying to
implement?
-igor
On Tue, Mar 26, 2013 at 8:07 AM, Marco Springer <ma...@glitchbox.nl> wrote:
> Hi,
>
> Lets say I have about ~100.000 of MarkupContainer objects that I want to put
> into a ListView or RepeatingView.
> This works fine functional wise... It's rather slow though.
>
> It boils down to:
> MarkupContainer:
> 1309 private Component put(final Component child)
> 1310 {
> 1311 int index = children_indexOf(child);
> 1312 if (index == -1)
> 1313 {
> 1314 children_add(child);
> 1315 return null;
> 1316 }
> 1317 else
> 1318 {
> 1319 return children_set(index, child);
> 1320 }
> 1321 }
>
> and the call to "children_indexOf(child)" where it loops over all it's
> existing children and compares the id's until a match is found.
> With an increasing amount of children this can get rather slow...
>
> I though off overruling some functionality in the MarkupContainer class since
> I'm sure that for this list of items the children will be unique in their id
> and don't need that lookup, and overruling the "put" or "children_indexOf"
> function would give me enough power to skip that performance impacting part.
> But most functions have private access, leaving me nothing to control the
> adding of child components to a MarkupContainer.
>
> Does anyone else have experience with adding rather large quantities to
> something like the ListView and/or RepeatingView?
> Or is there another way of rendering this large amount of containers?
>
> Thanks in advance.
>
> Kind regards,
> Marco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org