Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
QuasselDroid-ng
QuasselDroid-ng
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 66
    • Issues 66
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Janne Koschinski
  • QuasselDroid-ngQuasselDroid-ng
  • Issues
  • #93

Closed
Open
Opened May 19, 2018 by Shane Synan@digitalcircuit
  • Report abuse
  • New issue
Report abuse New issue

Add contextual reminders of missing needed core features

Steps

  1. Connect to a core missing needed features, e.g. CoreSideHighlights
  2. Accept the missing core features dialog
    • This includes tapping outside of the dialog, which can happen accidentally
  3. Access client notification settings, configure core highlights, etc

Expected

Some gentle reminder of missing core features that can be tapped to reveal the dialog again.

This hopefully reduces confusion for anyone who taps Accept/skips dialog, uses QuasselDroid for a while, then notices things don't work and wonders why. It also would solve the (admittedly contrived) case of connecting to a core missing one feature, restoring that core to an older backup missing more features, and having no way to see this in QuasselDroid.

Actual

The dialog only shows once.

Additional

Perhaps this could be integrated into the Core Info activity, with Settings providing some sort of tappable item to launch the core info window? A button/bar/activatable item there could then re-launch the missing features dialog.

The current approach seems fine for QuasselDroid in beta where people are more likely to pause to read dialogs as they expect new things, but this may want to be addressed before a full release.

Disclosure: I am biased given I've written a few contextual info/warning bars in the Quassel desktop client. I have no idea how well those work in practice.

Edited May 19, 2018 by Shane Synan
To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
Future Release
Milestone
Future Release
Assign milestone
Time tracking
None
Due date
None
2
Labels
Priority: Normal Type: Feature
Assign labels
  • View project labels
Reference: justJanne/QuasselDroid-ng#93