Sakai Design Patterns Library WG / UI Roadmap WG Weekly Meeting
2007-08-20/21 at 23:00 UTC time (3pm PST/6pm EST/8am Sydney)
Facilitator: Colin
Note taker: ?
Conference Call Info
Dial-in #: 812-856-7060
Conference ID: 350 #
Pin: 72524 #
Agenda
- Shaw Han and Allison's More Sites Mockups
- Review existing Design Patterns so group can mark them finalized and live: 'Page' section at http://issues.sakaiproject.org/confluence/display/DESPAT/Library
Notes from last meeting
Eli's List Builder Example
- Eli has an example of a DHTML List Builder implementation.
- Kathy mentioned that she feels like perhaps the example should include items in both sides of the list: much of the interaction complexity
- There were some questions about what the best way to provide an indication that the item was moved:
- Should it be moved out of the left hand list and into the right?
- Or should it be greyed out as is the current behaviour?
- Colin pointed out that this is one of the those "it depends" answers; Daphne mentioned that we should look at some of the scenarios for correct behaviour and document them in the pattern
- Colin pointed out that it could be more flexible in terms of screen magnification; is willing to help
- Decided that this should be listed as an implementation of the List Builder pattern
Mike's Accessibility Improvements
- Talked briefly about Mike's improvements to design patterns accessibility. So far, they look great. Will discuss it further when Mike is back from vacation.
Review Existing Design Patterns to Promote Them
- Should we limit screenshots to the default skin? Or a canned skin?
- Decision: use the default skin for all examples and screenshots unless an alternate skin better represents some fundamental aspect of the pattern.
Fluid Design Patterns
- What is the relationship between designers across projects?
- The things that make them patterns is that you can use them in different contexts
- It would be nice to have the patterns shared across projects, but have the examples, implementation, and screenshots be customized for each project
- Colin raised the issue of making sure that the design patterns are something that each community can identify; that they best represent the kinds of UI activities that each project
Note taker/facilitator rotation: Allison, Colin, Daphne, Eli, Jackie, Judy, Julie, Kathy, Marc, Tim, Will