[Tickets #855] default first listing in the Browse

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=855
-----------------------------------------------------------------------
 Ticket             | 855
 Updated By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | default first listing in the Browse
 Queue              | Turba
 Version            | HEAD
 State              | Accepted
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2005-12-07 14:28) wrote:

> We don't currently have a preference for which page to start with 
> (instead of all), and we do filtering client-side. We should fix both 
> of those, but patches would help immensely.

Currently, the paging works based on the first character of the displayed
'name' field - which is dependent on the user's name format prefs.  How
would we go about filtering server-side without making assumptions about the
field structure on the backend?  In other words, we can check the prefs and
see we are displaying "Lastname, Firstname" but how can we search for this
server side - not knowing if there is a 'Lastname" field available, and if
it is, what is it called?  I thought of putting a 'paging_search' entry into
$cfgSources, but that would force the name format pref to be the same 
system wide, not per user...  We could put it into the user prefs, but would
something like this be intuitive to the user?

Thoughts?