This issue outlines the tasks that need to be done before the app is ready for a proper release.

• Assistant
  • Show message time (74df859)
  • Fix going into voice control mode (7374b66)
  • Add voice control GUI (11af560)
  • Send button in entry (cd56d28)
  • Auto-scroll to the bottom (ada8e3c, 591b1d3 - still kinda janky, will need fixes)
  • Stop recording when message is being typed/sent - should prevent issues with e.g. confirmation dialogs (743a698)
• Skills menu (9a77227, 91d24bb, more improvements yet to come)
  • Add skill icon display (26274a9)
  • Search (4a86978)
• Preferences menu (21fb7cb)
  • Websocket address selection (21fb7cb)
• About menu
• Wrappers
  • Image attachment dialog wrapper (e103c45)
  • Better handling for hiding suggestion wrappers (76c429b)
• Background daemon that allows the UI to show up when Mycroft is called, even outside of the app (84d51e0, 90a72db, 5ddd8ee)
• Pairing dialog (ce63001)
• Error handling (9475b7e)
  • Make it appear in all views, not just the assistant (610485f)
  • Lock view switcher buttons (4806696)
  • Add custom checker for Mycroft presence (193091b)
  • Re-create client when the connection is dropped (0ac7c60)
• Add commandline argument to start as daemon (ef2474a)

Postponed for next release

• TTS/SST settings? (Plasma Mobile seems to have something related, according to mycroft-gui commits - what is it, and does GNOME offer something similar?)
• Text parsing workarounds (many skills, such as showing the IP or installed version, change the text to make the numbers more readable to text-to-speech - we need to turn it back to a more readable form)
• Proper Flatpak support

hello! just found out about this project thanks to @PureTryOut

i am not familiar with GTK or with this code base, i took a quick look at the repo. apologies if my terminology is off or i misunderstood something

my suggestion is that this is made to support all the SYSTEM_XXX.qml equivalents, these correspond to templates commonly used by skills, eg, self.gui.show_image, self.gui.show_text, docs here and can be easily parsed from the requested page name

regarding the hardcoding of skill_ids to views, i wonder how we could best allow skills to provide this (optionally)

gui_wrappers = {
    "mycroft-fallback-duck-duck-go.mycroftai": AnswerImageWrapper,
    "mycroft-wiki.mycroftai": AnswerImageWrapper
}

we have been discussing the best way to support other GUIs that don't use QML such as javascript or command line interfaces, the easy implementation would be to check if the skill provides a equivalent named file with different file extensions, ie

• .qml
• .ui
• .html
• .jsx

if we implement this in ovos, would the .ui format seen here be the way to go from skill developers side if they wanted to explicitly support lapel or other GTK based gui clients?

The main issue is how we're going to include Mycroft libraries. (While leaving the server bits to be handled outside the container seems fine, remember we still need the mycroft module itself for some things.)

There are three problems with the current popup:

• it doesn't show the messages, only opens the full app
• it doesn't always work on all compositors (for example, when fullscreened on Phosh the background is black rather than transparent)
• and in general, it looks ugly on anything that isn't a phone display.

We need a better design for the pop-up.