The best practice of remembering previous selections when doing paginating?

[Emily Gu <e2...@gmail.com>]

Hi,

I have one question for you. For the solution posted on wiki page of large
data set <t:dataTable>, when you select several rows on the first page, then
go to the next page, the selection is gone. It only knows what selected in
the current page. I have two questions now:

1. What is the best practice in doing such web pages. Should it remember
stuff selected from the first page?
2. How to do it in using <t:tableData> with <t:dataScroller>?

In my opinion, it would be nice if we can remember the selections of
previous visited pages if the data are related.



Thanks,

Emily

Re: The best practice of remembering previous selections when doing paginating?

[Emily Gu <e2...@gmail.com>]

Thanks for your reply. I will try that.

Emily


On 3/24/06, Aleksei Valikov <va...@gmx.net> wrote:
>
> Hi.
>
> > I have one question for you. For the solution posted on wiki page of
> > large data set <t:dataTable>, when you select several rows on the first
> > page, then go to the next page, the selection is gone. It only knows
> > what selected in the current page. I have two questions now:
> >
> > 1. What is the best practice in doing such web pages. Should it remember
> > stuff selected from the first page?
> > 2. How to do it in using <t:tableData> with <t:dataScroller>?
> >
> > In my opinion, it would be nice if we can remember the selections of
> > previous visited pages if the data are related.
>
> I usually add a column with a checkbox that adds/removes row id from the
> set. The set is saved somewhere in a session-scoped managed bean.
>
> If your selection is no longer one-page-scoped (request-scoped), it's
> time to move its storage to a session-scoped bean.
>
> Bye.
> /lexi
>

Re: The best practice of remembering previous selections when doing paginating?

[Aleksei Valikov <va...@gmx.net>]

Hi.

> I have one question for you. For the solution posted on wiki page of 
> large data set <t:dataTable>, when you select several rows on the first 
> page, then go to the next page, the selection is gone. It only knows 
> what selected in the current page. I have two questions now:
>  
> 1. What is the best practice in doing such web pages. Should it remember 
> stuff selected from the first page?
> 2. How to do it in using <t:tableData> with <t:dataScroller>?
> 
> In my opinion, it would be nice if we can remember the selections of 
> previous visited pages if the data are related.

I usually add a column with a checkbox that adds/removes row id from the 
set. The set is saved somewhere in a session-scoped managed bean.

If your selection is no longer one-page-scoped (request-scoped), it's 
time to move its storage to a session-scoped bean.

Bye.
/lexi