[Building Sakai] Proposed changes to Roster2

Adrian Fish adrian.r.fish at gmail.com
Wed Oct 29 09:47:07 PDT 2014


I should point out to everybody that Roster2 is the roster tool that ships
by default with Sakai 10 onwards, so if you're running >=10 or intend to
soon, it's important that you have a look at the changes proposed.

On 29 October 2014 16:07, Sam Ottenhoff <ottenhoff at longsight.com> wrote:

> I like your direction here and definitely support simplifying views.
>
> If I had a huge course, I imagine my main use of Roster would be via the
> search.  I would want to see picture/profile info of just one student and I
> would type in part of their EID or firstname/lastname to find them.
>
> Infinite scroll also makes sense to me.  When I'm on a mobile device, I am
> becoming very comfortable with this Twitter-like pattern of scrolling down,
> waiting a second for more data to load, and scrolling more.  It seems a lot
> more intuitive than tiny pager numbers while on mobile.
>
> On Wed, Oct 29, 2014 at 12:00 PM, Adrian Fish <adrian.r.fish at gmail.com>
> wrote:
>
>> Hi all,
>>
>> Juan José and myself have been having a think about how to implement
>> paging of large number of site members in Roster2. I was thinking along the
>> lines of the standard paging control, whereas Juan was thinking of
>> implementing an infinite scroller with lazy loading of the user data. I
>> think his idea is the best as it's simpler than messing around with paging
>> controls and will just look a lot more modern. I'm also thinking of adding
>> an autocomplete box where a tutor could just type a name and get some
>> matches back.
>>
>> Here are the (mainly mine, apart from the scrolling) proposed changes,
>> one by one:
>>
>> 1. Infinite scrolling on the list of roster members, with lazy loading of
>> the members.
>> 2. A search box which auto completes on matches, to allow single members
>> to be retrieved easily, without scrolling the entire list.
>> 3. Get rid of the sorting stuff, currently in the table headers, like
>> sorting on role, etc. Infinite scroll makes table sorting redundant.
>> 4. Add a filter box to the overview page, to filter on role - role still
>> seems a useful thing to filter on.
>> 5. Remove the group membership area, just show that stuff in the overview
>> page.
>> 6. Remove the pictures area, show pictures in the overview page,
>> permissions permitting.
>>
>> In other words, all the views are collapsed into two, home and
>> permissions. You just end up with an infinitely scrolling ( if you have an
>> infinitely big site :) ) page of members, with data filtered on permissions.
>>
>> I think this will be a very nice cleanup and will make the roster tool
>> look a lot more up to date.
>>
>> Cheers,
>> Adrian.
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20141029/33e00a35/attachment.html 


More information about the sakai-dev mailing list