Matt Pasiewicz wrote:
> > 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.
Let me think more about that one. There are already quite a few settings
and I'm afraid of making the header / footer look too complex.
> 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.
Now there's ex:pagingControlLocations = top / bottom / topbottom.
> > 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.
Maybe you could use Page Speed
http://code.google.com/speed/page-speed/
to see which parts have been sped up.
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
-~----------~----~----~----~------~----~------~--~---
