Thanks for the solution. Tho I forgot to mentioned that one of the
requirements for the UI is to avoid paging. We would like to show a
long list and let users scroll using the browser's scroll bar. I would
definitely give a try at the showcased examples. Are there any other
workarounds for this?

thanks very much

On Jul 10, 10:59 pm, Tony Rah <[email protected]> wrote:
> Attach a paging control to your cell widget and page say 10 or 20 rows
> at a time. You can also adapt paging to the scroll bar so the user
> doesnt have to press buttons. When the scroll gets to the end it will
> render the next page. There are samples in the gwt showcase to give
> you an idea how it all works.
> On Jul 9, 9:28 pm, Potate <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi
>
> > I have 100+ rows to render in a celltable. The actual data is
> > downloaded quite fast via RPC call. However, rendering these 100+ rows
> > in IE6 is awfully slow. It also causes temporary UI lockups. Is it
> > possible to render the table in chunks? maybe like 10 rows at a time
> > incrementally? I tried the following but it doesn't seem to work in
> > IE6. I still get lockups:
>
> > Scheduler.get().scheduleIncremental(new RepeatingCommand() {
> >             int cur = 0;
>
> >             @Override
> >             public boolean execute() {
> >                 int size = data.size();
>
> >                 List<OrderEntry> batch = data.subList(
> >                         cur, Math.min(cur+BATCH_SIZE, size));
>
> >                 tableDataProvider.getList().addAll( batch );
> >                 tableDataProvider.flush();
>
> >                 cur = cur + BATCH_SIZE;
> >                 if (cur >= size-1) {
> >                     // force a sort
> >                     ColumnSortEvent.fire(table,
> > table.getColumnSortList());
> >                     return false;
> >                 } else {
> >                     return true;
> >                 }
> >             }
> >         });
>
> > also, I'm forcing a sort to put the sortable headers in the right
> > state, even tho data got back from the server is already sorted. is
> > there a way to avoid it?
>
> > thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to