Thanks All. That pretty much covers all possible options. One other that came though pm was to faux paginate using JS. Technical limitations aside, its probably not a good idea to take actions on elements you can't see. So I would either stick with the detault behavior or use a container to store items. Mark, I agree with your logic. It is the context that lends itself to the container approach. The list is long- could be dozens of pages even with a large # of items on a page. Its also one of the primary actions in the tool. Repeating it multiple times will not work in this instance.
-Vishal On Mon, Dec 15, 2008 at 1:11 PM, Mark Young <[email protected]> wrote: > Why are the items being selected in the first place? Could the > selection be used or applied before moving on to another page? If the > selected items might span many pages, could the process be broken up > into smaller pieces that are performed per page? > > > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > Posted from the new ixda.org > http://www.ixda.org/discuss?post=36441 > > > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [email protected] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
