Sakai Design Patterns Library WG / UI Roadmap WG Weekly Meeting
2008-02-6/7 at 23:00 UTC time (3pm PST/6pm EST/8am Sydney)
Facilitator: Tim
Note taker: Allison
Conference Call Info
Dial-in #: 812-856-7060
Conference ID: 350 #
Pin: 72524 #
Agenda
- Prioritization of UX issues (a.k.a. not just letting the mailing list dictate our priorities/things we work on...thinking about the UX Spreadsheet)
- Weekly UX Newsletter (featured current issue, featured spreadsheet issue, featured design)
- Take turns creating it each week
- Discuss Michael Korcuska's requirements proposal
- new items on the Sakai UX Issues and Discussions list
- the remove vs. delete issue
- inventory of tools which save state vs. those which don't, & determining whether there are any dangerous use cases where users may lose data because of this (we thought of a couple, but have not verified them yet)
- understanding the dependencies on Resources
- update on Pager
- update on Design Patterns
Present: Clay, Eli, Allison, Daphne, Barbara, Erin, Shaw-Han, Tim, Kathy
Next Steps:
Note taker rotation: Allison, Barbara, Daphne, Eli, Erin, Jackie, Judy, Julie, Kathy, Shaw-Han, Tim, Will
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 (there is a "Copy" function in the Info tab) to create the next meetings agenda (make this a sub-page of "Meetings"). Update the agenda with any known items and included To Do's Strip out the notes section. (And leave this note for the next note taker.)
Meeting Notes
- Going forward, we will use the notetaker rotation to decide who the notetaker will be, starting with Allison.
- UX Lead Nathan Pearson hired - Clay says he's going to start by talking to people in the community to get ideas on what the initial project will be. Eli thinks Michael will send out a letter to the community to announce Nathan.
- Newsletter
- could send out before UX Meeting to get people to the group
- could discuss solutions to issues that come up on the mailing list
- what about a blog? - Fluid does have a WordPress blog running on their server now. UC Berkeley also has a blog and it may be something we can host here (along with Confluence & JIRA we are adding).
- Design Patterns
- Work on the Design Pattern Library & DP working group are on hold for now while Fluid focuses on contextual inquiries. Hope to be back to it in a month or so. In the meantime Kathy and volunteer Justin may be able to work on it.
- Kathy very busy, moved from Applications department to User services
- Pager
- Erin has been working on some other designs, which are on the Fluid Smart Page Navigation wiki page: http://wiki.fluidproject.org/display/fluid/Smart+Page+Navigation+%28aka+Pager%29
- Mock-ups are ready for paper prototyping and user studies
- There is a new design for the slider pager
- click on a letter to see just that letter
- can stretch slider to show more letters and the "show x per page" changes to show how many are there
- can change "show x per page" which changes the slider to match
- Daphne points out it's not easy for the user to "go to the next page", but Erin says that's why it snaps, so it goes to the next set of items
- She doesn't think slider works well with a table that has many columns it can be sorted by
- If you sorted by User ID, you could sort by what is showing, but it may not be the best solution as that would create inconsistency across the app (normally it sorts within all the items).
- Another option might be to change the slider to User IDs when you sort by User ID, but this could be hard with alpha-numeric user IDS.
- sliders can work well but only in some cases: e.g. don't create sliders in situations when users want to sort on other columns
- concern when you snap it that you missed some people
- Tim thinks this is similar to the remove vs. delete discussion ... consistency
- Clay: apps give two different views on things, macro & blown-up, use macro where you are zoomed out to to large scale sweeping nav and the other to do detail work. Slider could go on left side to allow users to quickly jump to sections.
- iTunes: coverflow and library is similar
- Ultimately wants one good design for page navigation, play with parameters like # of items shown on a page. Ideal would be to have just one which would fulfill all needs.
- Resources
- Understanding how other tools rely on Resources, what functionality lies in Resources, this is needed to help folks re-think Resources, and make changes to it in the future.
- Next week
- We need to create an agenda in order to make sure we have a productive week
- Let's have everyone read beforehand and talk about Michael Korcuska's Requirements proposal