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
reier...@gmail.com wrote:
Hi,
Angular is just a detail on the approach I was
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
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 vineetsemwa...@gmail.comwrote:
hi ,
do you mean removing items when
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
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
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{
1311int index
putting a 10 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
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
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
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
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 ListViewT into a ListViewListT and
splitting the original dataset into say 10k List#subLists. It ain't pretty,
but for a (nearly finished) app, it beats a
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,
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
reier...@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.
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
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
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
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
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
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
On Tue, Mar 26, 2013 at 5:11 PM, Igor Vaynberg igor.vaynb...@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
On Tue, Mar 26, 2013 at 5:33 PM, Eric Jablow erjab...@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:
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
22 matches
Mail list logo
