Yep, this seems to be a good idea! I'll add this as an option to the tree. As I still would like to keep the number of items per page limited I'd propse to present the child when expanded like this (pagesize=5): - Numbers - Integers ... ----- ...more (click to collapse) ----- 56 ----- 57 ----- 58 ----- ...more
On 25 Nov., 15:57, Bruce Johnson <[EMAIL PROTECTED]> wrote: > On Tue, Nov 25, 2008 at 8:33 AM, dflorey <[EMAIL PROTECTED]> wrote: > > > Hi Bruce, > > have you seen that you can easily navigate to the parent node by > > clicking on one of the dotted lines (links) on the left hand side of > > the leaf? > > I see that it works, but it still doesn't really address the general > question of giving the user a clear sense of context. > > It seems like this would be better as an "infinite scroll" to achieve the > effect of on-demand loading without forcibly breaking things across pages. > If there happened to be a really large number of children for a tree item, > perhaps we could introduce a notion of an ellipsis in the child list, like > this: > > - Numbers > --- Integers > ----- 1 > ----- 2 > ----- ... (click to show all) > ----- 99 > ----- 100 > > That way, you could keep the hierarchical context for easy skimming of the > overall structure, yet the user can drill down explicitly when they have > enough of an idea about where they want to look. It's sort of like cold > folding in IDE. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
