Repository navigation
Add simulator discovery and setup interface - #6
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.
Replace the launch placeholder with a Discover screen that checks for available iOS simulators, lists their runtime and power state, and provides setup guidance when none exist. Offer Xcode installation through the App Store when Xcode is missing, distinguish toolchain errors from an empty inventory, and open Device Hub or Simulator from the selected Xcode installation. Refresh on app activation, with the refresh button, or with Command-R.
Keep branding, navigation, and the repository link visible while long simulator lists scroll independently. Constrain both split columns to the window viewport, keep the toolbar status inside its background, and center discovery states across the whole detail area. The empty-state illustration uses the tablet and phone without a button-like plus badge.
Separate the sidebar, no-simulator guidance, missing-Xcode guidance, and discovery status views into dedicated SwiftUI files. Keep window composition, discovery state, and action handling in
ContentView.Validation:
swift-formatchecks passed.