-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Redesign] SDK changes #269
Conversation
Generated by 🚫 Danger |
d227266
to
31a5a05
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great 👍 I added few comments, mostly around using multiplies of 8, checking the docs and other nits. Also, please check why the tests are failing. Will also use it a bit in my next meetings.
TopRightView { | ||
Text(value) | ||
.minimumScaleFactor(0.3) | ||
.frame(width: 14, height: 14) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make it 16? 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Designers seems to be using values that aren't multiples of 8. Even Apple isn't using multiples of 8 for sizes(button sizes have been historically 44 and 50) but probably only for margins (8 and 16). Even the article states that the point of it is 1. consistency (which means that design will need to be updated to match that) and 2. used for grids and spacing(doesn't mention sizes)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok for size, but I think we should be consistent with paddings - they should be multiplies of 8. Can you also discuss this with the design team?
Sources/StreamVideoSwiftUI/CallView/LayoutComponents/Controls/ModalButton.swift
Show resolved
Hide resolved
...es/StreamVideoSwiftUI/CallView/ViewModifiers/ReadableContentGuide/ReadableContentGuide.swift
Show resolved
Hide resolved
@@ -97,7 +97,7 @@ struct IncomingCallViewContent: View { | |||
Button { | |||
onCallRejected(callInfo.id) | |||
} label: { | |||
images.hangup | |||
Image(systemName: "phone.down.circle.fill") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we change this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the Image we have in the Images is now the one without the circle.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can expose a different image, sth like incoming/outgoing hangup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't that be confusing? Ideally we should be using the same hang up button we have as shared component, right?
Sources/StreamVideoSwiftUI/Utils/ReadableContentGuide/ReadableContentGuide.swift
Outdated
Show resolved
Hide resolved
5089918
to
48aef00
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there, we just need to update the padding and some color nits. Also, the CHANGELOG needs to be updated (redesign + the changed methods). Did you check the tutorials (if we use the modified methods there)? We can also release a new minor version after we merge this.
Sources/StreamVideoSwiftUI/CallView/ScreenSharing/ScreensharingControls.swift
Show resolved
Hide resolved
.resizable() | ||
.foregroundColor(colors.text) | ||
.aspectRatio(contentMode: .fit) | ||
.padding(10) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, we should fix this, in Figma the padding is 8.
Sources/StreamVideoSwiftUI/CallingViews/MicrophoneCheckView.swift
Outdated
Show resolved
Hide resolved
232e724
to
e336ae5
Compare
Co-authored-by: runner <[email protected]>
3a173fb
to
2dc4424
Compare
Quality Gate passedThe SonarCloud Quality Gate passed, but some issues were introduced. 5 New issues |
🎯 Goal
Provide the SDK changes required for the new redesign of the components and Demo App.
🛠 Implementation
Provide a detailed description of the implementation and explain your decisions if you find them relevant.
☑️ Contributor Checklist