Show profile setup choices on first launch - #84
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With no configured profile, Parla opens an empty chat list and tells the user to find the profile menu. Show the existing setup choices directly on the welcome screen: create a profile, import/link one from another device, sign in with an email address, or use an invitation code.
Reuse the same choice list in the Add Profile dialog. Keep the welcome choices available after cancellation and restore them when the last configured profile is removed. Focus the first choice, keep the empty sidebar out of the way across window resizing, and restore the chat list once a profile is ready. Update the onboarding documentation and remove the old instruction to open the profile menu.
Start the shared event loop with no selected account so first-profile creation and linking receive progress events. This includes the same event-loop startup adjustment as #82, which can be merged independently.
Validation:
webxdc=false.git diff --checkpasses.Fixes #25.