Sakai Design Patterns Library WG / UI Roadmap WG Weekly Meeting
2007-07-02/03 at 23:00 UTC time (3pm PST/6pm EST/8am Sydney)
Facilitator: Daphne
Note taker: Jackie
Conference Call Info
Note different number
Dial-in #: 812-856-7060
Conference ID: 350
Pin: 72524
Password: 5624
Agenda
ToDo's and notes from last meeting
-
- We need to identify design pattern status at 3 levels: 1) Kick's ass, 2) Needs work, 3)In progress
¿ Will will come up with semantic language we want to use.
- We need to identify design pattern status at 3 levels: 1) Kick's ass, 2) Needs work, 3)In progress
- New design patterns:
o Row Striping - Judy by September
o Jackie & Julie will likely be busy through October but they are signed up for a couple.
o Print - Eli will look at this to understand where/if it makes sense to create a design pattern for this. Include the idea of preview and building in affordances to allow users to know the functionality is available.
Notes
Present: Daphne, Allison, Judy, Eli, Will, Mike, Tim, Luke
*Ways to indicate status of design patterns decided: "Endorsed" (green checkmark, as "Kicks ass"), "Under development" (yellow caution sign, yellow triangle, was "In progress"), "Incomplete/On Hold", i.e. because the person working on it moved on to another project (red question mark, was "Needs work").
*Will asks if its possible to do row-striping in javascript? Mike says to avoid it whenever possible. Decision to put off discussion of implementation for now.
*Selecting from list patterns:
Luke brought up the 2 design patterns they're thinking about implementing to allow instructors to do course sl3ection 1) swap box (called "List Builder" by Tidwell) i.e. left list to right list--some usability issues with it. Alternative: scrollable list of all courses, filter them down (e.g. by dept), checkbox next to the ones to select. (See http://mxdev.chitester.weber.edu/designPatternQuestion.html). Lots of discussion on these patterns; Daphne suggests doing some user testing. Luke will talk with co-workers to see if can make available their mockups (or will create prototypes) so some of us could do the user testing locally.
*Question about Add Participants functionality (in Site Info):
Q: Currently need to know user id to add them to site; will this change? Searchable list would be helpful. A: This has been a request since the beginning of Sakai; nobody is working on Site Info right now.
*Mike will send around (to DG) link to 2.3 accessibility testing report.
*Will (editing Responsive Disclosure pattern): when design pattern refers to following "accessiblity considerations", can we link to a cannonical accessiblity source? Action item: Mike will find and add the link.
*Tim asks if we can keep our examples current (still referring to Responsive Disclosure which shows screenshots from old version of Resources)? Action item: Will will look for something and put it in, unless somebody contacts him with a better idea. Daphne also suggests that Will ask UI DG. Daphne will also look at current Gradebook design to see if there's anything there.
Agenda:
Note to note taker: On the Home page, please make these notes the "Last meeting's notes" link and increment the next meeting date and agenda link. Also, once you are done with these notes please duplicate and this page to create the next meetings agenda. Update the agenda with any known items and included ToDo's Strip out the notes section. (And leave this note for the next notetaker.)
Note taker/facilitator rotation: Colin, Daphne, Eli, Jackie, Judy, Julie, Kathy, Marc, Tim, Will
Note taker rotation: Colin, Daphne, Jackie, Judy, Julie, Kathy, Marc, Tim