DISCUSSION: Modulerize Setup Process

[AIIX]

The current setup skill is based on a sequence of events, from welcome screen to end of setup, each backend is also tied into its own process (maybe a separate issue).

Current Process:

• Setup Loading Screen (Transition between wifi and setup skill)
• Welcome Screen
• Language Selection Screen (Currently Disabled By Default)
• Backend Menu Selection Screen
• Selene Backend -> Own Pairing Process Screens -> End
• Personal Backend -> Own Process -> End
• No Backend -> STT Selection -> TTS Selection -> End

Proposed Changes: Modularization of the setup process, specifically let images decide what modules to show. We can define the current setup process in a break down of modules into default_modules list to display by default if image wants or advance_modules list

Default Modules:

• loading (transition) (not optional)

• welcome (optional, preferred: enabled & in default)

• language (optional, preferred: enabled (when available) & in default)

• backend: (optional, preferred: enabled & in default) -- If Backend is enabled then:

  • allow the backend to take over its own pairing / setup process at least for (Selene, Personal Backend),
  • If no backend is selected show quick_setup_no_backend

• quick_setup: (optional, preferred: disabled & in default) (allows users to skip or continue to advanced config)

• quick_setup_no_backend (not optional if backend is enabled, not needed if backend is disabled, allows users to use defaults set by image or continue to advanced config) (preferred: enabled & in default)

Advanced Modules:

• tts (optional, preferred: advance)
• stt (optional, preferred: advance)
• ww (optional, preferred: advance)
• timzeone and location (optional, preferred: advance)

All module handling will be done by module loader that will read the list of modules to load and show them in that order, All ui "next" actions will be connected to this module loader next action

[NeonDaniel]

In addition to this, maybe we could have some bus API to call specific steps? Some example use cases:

• user skips internet, they might ask to set time/location via intent
• user changes language via some other skill or plugin which could launch STT or TTS menu with compatible plugins

[AIIX]

In addition to this, maybe we could have some bus API to call specific steps? Some example use cases:

* user skips internet, they might ask to set time/location via intent

* user changes language via some other skill or plugin which could launch STT or TTS menu with compatible plugins

Do we want to have this accessible via drop down menu in advanced config or something, then maybe the bus API should call those menu to show (separate pages) ? instead of starting the setup process again ?