Clean up code in InfoPane to be more robust#436
Conversation
|
Hi @thai-d-v First of all thank you for taking the time to make Xcodes better! I'm all for making The main question I have is around all the Thanks again - let me know how I can help |
MattKiazyk
left a comment
There was a problem hiding this comment.
See comment - really awesome start - just questions around the WrapperView
|
Hi @MattKiazyk,
|
|
@thai-d-v thanks for the response. I see some benefit in it, however I would rather stick with the Apple way of using different previews for each view you are previewing. Added benefit would be that the view you are working on can be previewed as you are working on. In the WrapperView scenario, I would have to change the state PreviewName to be the one I'm on every time I wanted to edit and preview. Feel free to use the |
- I moved outside 2 lines of `.frame(maxWidth: .infinity, alignment: .leading)` because this layout job should belong to `InfoPane`
- I added preview blocks for testing
- narrow down interfaces of some functions
rebase main
- I move `UnselectedView` out to:
1. narrow data dependency
2. `InfoPane` should only care about displaying data, not whether an `Xcode` is selected
…e it self-contain
3e8f67f to
a596e5f
Compare
|
@MattKiazyk You're right, code looks much cleaner with |
|
Can you please remove me from this mailing list????
…On Thu, Nov 23, 2023 at 12:35 PM Thai D. V. ***@***.***> wrote:
@MattKiazyk <https://github.com/MattKiazyk> You're right, code looks much
cleaner with #Preview. I updated it.
—
Reply to this email directly, view it on GitHub
<#436 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE2MTBFGJID6HI3Z642YOD3YF6COFAVCNFSM6AAAAAA6AD7U7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRUG43DIOJWG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Problem of
InfoPanebodyis too bigApproach
I move subviews to separate files
I fix
InforPaneUnselectedViewout to:InfoPaneshould only care about displaying data, not whether anXcodeis selectedDiscussion