July 20, 2006 Agenda and Minutes

Owned by Former user (Deleted)
Last updated: Jul 20, 2006Version comment
2 min read

Tentative Agenda

Mapping out the work ahead

  • Turn date widget into velocity macro
  • Changes to tool UI
  • Support for saving decisions by instructor
  • Changes to how user access is decided
  • QA - when would that need to start?

Quick review of CARET patch (can you talk about this, Francette?)

Minutes

What's our timetable?

  • Count back from delivery date of Aug. 21:
    • say 2 weeks of QA
    • then development work will need to have been completed by the end of the first week in August
    • which leaves roughly 2.5 weeks for development, and with Jim and Zach on vacation.
  • Jim: I still think this is doable. I've thought through the development work, and it's really just a matter of a few days. As I've emphasized throughout, it's the design that's the hard part of this work.
  • Jim: Zach said he had some experience with Velocity, but given that he's going to be away during this period, I'll just do it. It won't be too difficult.

QAing date widget JS - UNISA will do this tomorrow.

Sort Order

  • Is it confusing if different folders are sorted in different ways?
    • people are used to seeing different arrangements all the time
    • as a general rule, resource names aren't really helpful for finding things anyway
  • Do we have a design decision? Jim has a picture of things, but he's not sure we all have the same picture.
  • Mike is going to come up with some mock-ups.
  • Netflix text fields can be puzzling - if you try to make a number of changes before updating, or scrolling back and forth to double-check your number placements, uncertainties about what happens when several things are getting shifted at once.
  • Blackboard-like dropdowns lead to a lot of scrolling

2 proposed sort order UIs from end of meeting (will need mockups)

  1. Reuse and improve existing sorting interface
    • Use the sorting arrows from Sites -> Pages
    • Take out the per-action round-trip and handle with JavaScript
    • Once sorting done, post changes via Finish/Update/Save button
  2. Keep sorting in a similar context to Resources display
    • Use ideas from http://bugs.sakaiproject.org/confluence/download/attachments/19437/sort2_76.gif
    • Similar display to resources
    • Use radio-buttons to "activate" a row for moving
      • Activated row gets highlighted (as well as semantic property for screen readers?)
      • Controls appears to change postion - either textual "Move up/Move down", arrows, or both?
    • Once sorting done, post changes via Finish/Update/Save button