Thanks for bringing this up Harriet! This conversation brings up an important design challenge for Fluid components. Fluid components will live in many different contexts. Those contexts likely require different interface or interactions in some portion of the component (ex. the button conversation here). Our strategy is to identify those places where the interface or interaction are likely to change by context and make them configurable (with good defaults of course -- based on most common cases). The button labels for pager are a good example. It will be up to implementors to determine the best label given their context (i.e. date driven material, alphabetical, numerical). The design pattern for paging should discuss the different contexts and suggest appropriate labels. The components and design patterns work well together in this way.
Erin, perhaps we should add a task for the pager to identify the various types of data that may be "paged" so we can include design suggestions in the pattern. -Daphne On May 28, 2008, at 9:26 AM, Colin Clark wrote: > Hi Harriet, > > On 28-May-08, at 11:59 AM, Harriet Truscott wrote: >> We have gone with the Fluid pager design for our MySakai widgets. > > Glad to hear our early pager designs were useful to you. We've > actually got three different potential designs, all located on this > page: > > http://wiki.fluidproject.org/display/fluid/Smart+Page+Navigation+(aka+Pager) > > Which one of them have you implemented? > >>> Is the logic of the "previous" and "next" buttons on the >>> 'recent activity' pane the wrong way around? >>> >>> Given that this list should show most recent first, the "next" >>> willl be earlier in time - which is also "previous"! It might >>> be better to say "earlier" and "later" to name those buttons >>> less ambiguously >> >> I like 'earlier' - I think perhaps that 'more recent' might be >> better than >> 'later', alhtough > > Good questions. This is all a bit abstract until we can see the > designs in context. Do you have any examples of how you've implemented > the pager? Screenshots? > >> What do people think to this, and would you contemplate making an >> official >> Fluid suggestion for this context? > > I'm not sure our role is to provide "official Fluid suggestions," for > other people's software, but we're always happy to share our advice > and experience. :) > > Colin > > --- > Colin Clark > Technical Lead, Fluid Project > Adaptive Technology Resource Centre, University of Toronto > http://fluidproject.org > > _______________________________________________ > fluid-work mailing list > [email protected] > http://fluidproject.org/mailman/listinfo/fluid-work Daphne Ogle Senior Interaction Designer University of California, Berkeley Educational Technology Services [EMAIL PROTECTED] cell (510)847-0308 _______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
