A Java 8 feature that lets us leave callback hell.

see Java 8 promises.

As it is only for API level 24, we're going to need the backport.

use onDrawerClosed() callback of DrawerLayout.DrawerListener instead of onNavigationItemSelected()

Desired state:

• Up navigation (arrow) always navigates back to the last fragment and acts as a cancel button. No delays!
• Save (check mark) writes the changes to the API and on success navigates up. May introduce a delay caused by the web backend.

The number one use case for Meetling is viewing Meeting Agendas. The overview should therefore be at the top level of the meeting hierarchy. Agenda and meta data editing fragments should branch from here.

• Fragments should manage their own state
• Get rid of fragment callbacks

• Use full screen dialogs for editing, see:
  https://material.io/guidelines/components/dialogs.html#dialogs-full-screen-dialogs
• Implementation hints:
  https://stackoverflow.com/questions/27074717/android-fullscreen-dialog-confirmation-and-dismissive-actions
• supersedes #12

Replace action button in MeetingFragment Toolbar

Refactor WebApi

• About Fragment
• Possible text: "Permission to use the Meetling name, logo, and colors kindly granted by Sven James"

Use Android SDK UI testing framework

This will enhance the discoverability of the item rearranging feature

Use CONTRIBUTING.md to be compatible with GitHub.

The PNG needs a transparent background among other things.

Steps to reproduce:

1. Create example meeting
2. Create new meeting via menu

See Google Calendar

see https://www.youtube.com/watch?v=ZLYzX0G0YKQ&feature=youtu.be

Change to the Manifest:

<uses-feature
  android:name="android.hardware.touchscreen"
  android:required="false" />

Tasks:

• Introduce proper ellipsis in Agenda View for Item titles and descriptions that are too long
• On click, expand the agenda item to a full view of the item texts
• put button on item view to switch over to edit fragment

TODO

• Catch and process email validation errors
• AuthCode Dialog
• Catch and process authCode ValueErrors (especially auth_request_not_found, email_duplicate, auth_invalid)
• remove-email
• submit suggestions/bugs

Needs

• Name
• Email
• Activity Feed
• Edit FAB

Automate the creation of a local meetling instance for testing purposes.
Possible solutions: Write script that ties in with android testing, use pure gradle

Current: Title in Collapsible Cardview

Target: Title always visible in collapsing title bar

Expanded Toolbar

Hamburger Menu |   | Action Buttons
----------------------------------------------
Meeting title [Ellipsis]
Description [Ellipsis]
More button
----------------------------------------------
Agenda-Tab  | Trash-Tab

Collapsed Toolbar

Hamburger Menu | Meeting title [Ellipsis] | Action Buttons/Menu
----------------------------------------------
Agenda-Tab  | Trash-Tab
----------------------------------------------

• create meetings overview page (1 meeting = 1 cardview)
• add hosts list view with meetings for each hosts (1 host = 1 cardview, expand to view meetings, delete button), accessible from menu drawer

depends on #14

[x] Class properties (user etc.)
[ ] UI state

Prerequisite for mention on Meetling's about page (Meetling itself can be self-hosted)

Components

• backend: host list with user id, auth secret
• Create "add host" dialog with link in menu drawer
• Select host dialog when creating meeting
• make meeting import (url handler) multi-host capable

When creating/opening a meeting on a server: call webApi.getUser() to obtain credentials