> I've implemented that in trunk/, to be released in the next release. @David ... that rocks. Seems to be working in table view. Very nice.
I'd also be interested in seeing an option to toggle between a "View First 25" and a "View All" option next to the pager. I'll also follow to John's comments/questions with some of my own. > Could the location of the pager be an option? I haven't checked yet, but perhaps just a separate class added to the corresponding pager group ... class="exhibit-tabularView-pagingControls top" ... class="exhibit-tabularView-pagingControls bottom" ... then it can just be controlled via CSS. > Would having the pager turned on (say for 20 items per page) improve > performance for Exhibits with several hundred records? I'm curious about this too. I have an exhibit w/ 846 records. In Chrome, it seemed like the initial load (after the working modal appeared) shaved off a second or so with paging turned on. In Safari, sorting seemed about a half second faster with pagination turned on. Seemed snappier, but not an order of magnitude difference. Still, a good step nonetheless. On Sat, Jun 20, 2009 at 8:26 PM, John Callahan <[email protected]>wrote: > > Thank you very much for this addition. I will definitely be using this > feature. > > I just tried it out on the latest versions of Chrome 2, IE 7, FF 3. > Worked great on the Tabular view but no luck on the Tile or Thumbnail > views. Maybe I'm doing something wrong but it seems very > straightforward. No significant messages in Firebug. Here is the > Exhibit I'm using (site is in VERY early stages of development): > > http://dev.dgs.udel.edu/publications > > > Some quick thoughts: > > 1. Could the location of the pager be an option? Something like > ex:pageLocation: "top", "bottom", "topbottom" (My preference would be > bottom as there's already so much going on at the top.) > > 2. Just a possible suggestion but you could use HTML list elements (ul, > li) and style them to look the same as now. This usually offers more > flexibility when altering the style. (not sure how you would add that > style and allow it to be overridden by local css files???) > > 3. Could you add a title (and alt) attribute to the page anchors to say > something like "Page 2" or "Go to Page 2". This would be for mouse > tooltips and screen readers. > > 4. Could you add an ID to the span tags surrounding the dots in between > the page numbers? When styling (such as inside an existing site), I > may want to remove them completely or use my own images, can be done > using getElementById(#spanid).innerHTML = ... I like how the selected > page has it's own unique class so that can be styled separately. > > 5. I noticed that the pager goes away if only one page is present. > Could the pager not disappear? Even if it simply stated "1" or maybe > have the some text grayed out saying something like "1 page in > results"... I'm not sure. From a user perspective, if the number of > results is very close to the same number as items/page, it can be > confusing. From a web design perspective, it's be nice is that area of > the page didn't move. > > > 6. Will this replace (and make obsolete) the showAll and > abbreviatedCount parameters in the Thumbnail view? If not, which would > take precedence? > > > 7. Would having the pager turned on (say for 20 items per page) improve > performance for Exhibits with several hundred records? It would save > time in writing to the browser but that's not very much. Just curious... > > > - John > > > David Huynh wrote: > > Hi all, > > > > A looooong overdue feature is pagination in tile, thumbnail, and tabular > > views. I've implemented that in trunk/, to be released in the next > > release. Here's how it works in the presidents example > > > > > > > http://trunk.simile-widgets.org/exhibit/examples/presidents/presidents.html > > > > The new settings for controlling pagination are > > > > paginate = true or false; default is false > > pageSize = items per page; default is 20 > > page = starting page index, from 0 > > pageWindow = number of pages before and after current page to show > > if the current page is far from the first page and/or the last page; > > default is 2 > > > > What pageWindow means concretely is this. If you're on page 5, and > > pageWindow is 2, then you see > > 1 ... 3 4 5 6 7 ... 9 > > That is, 5 - 2 = 3 and 5 + 2 = 7. > > > > If you've been dying for this feature, please help me test it before the > > next release. Just link to the trunk api: > > http://trunk.simile-widgets.org/exhibit/api/exhibit-api.js > > > > Thanks, > > > > David > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" 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/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
