Old Detail View Project 0.5 Proposals

This stuff used to live on DetailViewProject when we were planning 0.5; it's been subsumed by the plans for what we're actually doing. -Bryan

People

• DonnDenman
• BryanStearns

Implementation Proposals for 0.5 Detail View Features

• Polish Proposal is to do the P1 polish early on, since it includes layout. P2 items are stretch goals, and P3 will be defered until after 0.5.
  • Update Layout for narrow width and add scroll bar. (P1)
  • Upgraded Blocks and widgets. Create an Edit-In-Place widget for editable text (P2)
  • Use Table for From/To Area, so we can more easily add Sharing Status and ACL controls (P2)
• Upgraded From/To Area with Sharing Status. Proposal is to do the P1 and selected P2 items only for 0.5.
  • See the UI Design for an image showing some of the desired affordances with the new sharing model.
  • Account Validation. Assuming an underlying mechanism to do account validation, Proposal is to give Text-only feedback (P1) appending a character to the address. Feedback will be given when the user leaves the field, following the current scheme of appending a "?" after items that could not be validated. Validated items will show without any additional punctuation. Invalid addresses will display with a "?", valid Emails that have no associated account will display with "!". If the validation is not synchronous (P2), then addresses pending validation will show an asterisk "*", with an explanation in the status bar.
  • Adding or Removing Sharees Proposal: (P1) When edits are made to the Sharees list, the new sharees gets uploaded along with the collection during the next sync. The Send button is also enabled, and invites are sent to anyone newly added to the sharee list.
  • Minimal ACL Support. Proposal: (P1) Sharees can have three levels: Editor, Reader, and Off, for the entire Item Collection. When Off, the client no longer tries to sync that collection. Reader and Editor act the same way on the client, but changes made by when under Reader ACL cause a warning to appear on the client when the sync fails due to permissions. The Reader/Editor setting is only honored when syncing.
  • Sharer Status.
    • Proposal: Use a Text-Only way to show status (P1). Users with "Off" permission will be shown in parens. Editing out the parens returns the user to normal status. Users with Reader permissions will be shown in square brakets. Editing out the brackets enables Edit permissions.
    • Proposal: Given a table-layout for the From/To Area, use graphical indication for Sharer Status, and ACL settings (P2), instead of the Text-Only controls described above.
• Event Invite/Sharing Invitation Support
  • Proposal: Provide a simple text description in place of a preview of the collection (P1). The text description would include a simple text list of some of the items in the collection, E.g. Meeting Tuesday 3 PM, Beer Bash 4:30, etc.
  • Proposal: When an invite is received, a button appears in the body of the invite for accepting the invite (P1). Proposal: Without a button, clicking on a received invitation, in the text description, accepts the invite (P2).
• Toolbar Buttons that go with the Detail-View:
  • Send - Proposal: use this button instead of a button in the body of the Detail View (P1)
  • Attach - Proposal: Do not support attachments.
  • Fonts - Proposal: Do not support fonts.
  • Label - Proposal: (P2) clicking on the Label toolbar button brings up a Choice control that shows all Item Collections in the system. If the current Item is in a particular Item Collection, then that collection is shown with a check next to it, otherwise it's shown without a check mark. Selecting the collection in the Choice control changes the checked state, and also includes/removes the current Item from that collection.
  • Print - Proposal: Do not support printing of the Detail View
• Updated Markup Bar
  • Mail Status Flags (P3) Show the status of Mail Items - if replied, forwarded, etc.
  • Private Lock (P3) Flag an Item as Private, which means it will not be shared even though Item Collections that contain it may be shared.
• Date/Time Widget (P1) Combine current Text form of the StartTime^? field with the Duration field to make a Text-only version of the Date/Time Widget that does some mixed parsing of Date/Time/Duration. (P2) Build a custom wxWidget control, maybe by modifying the existing wxWidget: TimeCtl^?. (P3) Include a date/time parsing library of our own design, or based on some existing system from the open source world.
• Date/Time Support Elements
  • All-day checkbox. Proposal: (P2) support a single check box that makes an event all-day, and changes the date/time display to not include a start time or duration.
  • Reminder widget (checkbox, choice etc) Proposal: (P2) given support for user notification and timers, support a combo box with a set of reminder choices.
  • Repeat Occurances affordance. Proposal: Do not support for 0.5
  • Location affordance. Proposal - Do not support for 0.5 (P1). Make this a simple string (P2).

-- BryanStearns - 23 Nov 2004