Meeting 58, 14th of March, 2017
Open, NormalPublic

Description

Present:
Christian, Michael

Agenda

  • Outbox
  • CardDav account UI
  • People UI
  • people search
  • notes in phabricator
  • Kube Sprint
  • Notifications/Error handling/UI Feeback

Notes

Outbox

  • Discussed use of icons with Andreas
  • Actual email status is required from backend
  • We need feeback for:
    • send progress
    • send success/failure
  • Outbox will remain in bottom left corner and will remain a popup.
  • We need a way to remove emails from outbox (abort send, move to trash)
  • We need a way to edit emails from outbox (move to drafts and open in composer

Icons

  • Kirigami uses the icons that we install from kirigami
  • QQC1 uses the system theme
  • QQC2 has no icons
  • We want to always use breeze icons (as part of the default skin)
  • so we need to make sure that breeze icons are available in both dark and non-dark versions.
  • Perhaps we will just have to copy all icons that we need into kube.

CardDav account UI

  • We'll turn the IMAP into a Generic account that also contains CardDav settings.
  • Eventually this can be turned into a generic system that allows for configuration of all sorts of backends.

People UI

  • Only contacts for now
  • Michael will push, temporarily with only dummy data. We'll switch over next week or so.
  • A simple filter can be implemented in the model (since we anyways load all data in one go).

Autocompletion

  • We'll use a stripped down addressbook component
  • Autocompletion mode when typing
  • Multiselect mode when clicking add recipient or so.

Kube Sprint

  • 2017-04-18 - 2017-04-21 in Zurich

Notifications/Error handling/UI Feeback

  • As first version just show an overlay (we'll do that for success/failure notifications for starters)
  • We'll need a persistent area to show errors (possibly with a way to get to the error log)
  • https://phabricator.kde.org/T5564
  • Account can show sync status (operation in progress)
cmollekopf updated the task description. (Show Details)