You are right, it has a fairly niche use, and probably should be ordered to stay at least 100 yards away from the real Pivot framework, but someone else might find a use for it. It kind of works like the MS Outlook 2010 message list filter. At the very least it may point someone looking to create "composite" components in the right direction.
My next task will be to write a generic ComboBox (I saw someone ask for this earlier, and I'll need one myself if I end up writing my app using Pivot). Hopeful that component will be more useful to a broader audience. Can I suggest perhaps some sort of web forum to share stuff like this? Makes searching old archives a little easier than the mailing list. As for the custom List class, I like the whole seamless nature of that, but what event would I use to get more data? I guess as a spot near the bottom of my TableView became viewable in the containing ScrollPane? The downside to that is that the relative position and size of the scrollthumb inside the toolbar would change as I appended more records to the custom List -- but maybe that's still better than having to use record selectors? On Wed, Feb 24, 2010 at 7:42 PM, Greg Brown <[email protected]> wrote: > Hi Scott, > > Congrats - sounds like an interesting piece of functionality. From the > description, it seems like it might be somewhat app-specific, but also sounds > like a valuable example that others could learn from. We have actually been > having a discussion on the dev list recently about where code such as this > could be shared. Don't have anything definitive yet, but I imagine we will > soon. > > As for paging - this is always a difficult problem to solve. The biggest > challenge is that, unless you cache the entire result set on the server, the > contents of any given page can change across requests. I generally prefer to > use a stateless approach when possible. > > However, if you do need paged results, one way to do it would be to create a > custom List class that retrieves pages on demand. That way, you don't need a > dedicated paging toolbar, and the user experience is more seamless. >
