Between the UI issues of browsing enormous lists, the infrequency with which people go to new rooms, and the ridiculous inefficiency of querying large room lists (result sets not well supported, no way to get a count without getting the whole list), we need a new list UI concept.
Current thinking:
Bookmarks + a 'show all' button built into the header that loads up the rest of the room list (with result sets if possible). To avoid the "empty UI" problem that spark has, we'll need to make empty servers have something visible. Perhaps some text explaining how it works, and a larger browse button.
Maybe checkboxes when in show all mode to allow the user to set which rooms show up automatically?
Would it be too inefficient to query each room on the bookmarked list to get a count of people in it?
Between the UI issues of browsing enormous lists, the infrequency with which people go to new rooms, and the ridiculous inefficiency of querying large room lists (result sets not well supported, no way to get a count without getting the whole list), we need a new list UI concept.
Current thinking:
Bookmarks + a 'show all' button built into the header that loads up the rest of the room list (with result sets if possible). To avoid the "empty UI" problem that spark has, we'll need to make empty servers have something visible. Perhaps some text explaining how it works, and a larger browse button.
Maybe checkboxes when in show all mode to allow the user to set which rooms show up automatically?
Would it be too inefficient to query each room on the bookmarked list to get a count of people in it?