-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat: ui improvements #25
Conversation
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 by me. Let's try to show it to product before merging, though.
it feels a little too tall, but I don't have an alternative to suggest
ui/src/components/Trade.tsx
Outdated
import { FormEvent, useState } from 'react'; | ||
import { stringifyAmountValue } from '@agoric/ui-components'; | ||
import scrollIcon from '../assets/scroll.png'; | ||
import istIcon from '../assets/IST.png'; |
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.
Do we have .svg
handy?
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.
Updated to use svg
<div className="row-center"> | ||
<Item | ||
key="IST" | ||
coinIcon={istIcon} |
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.
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.
Agree, maybe a ticket to use <NatInput />
is worthwhile. But I'm not sure if that comes with styling.
I'd like to see how it looks with the give / want side by side. Is it obvious to you how to do that? |
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.
Approving because it's an improvement. Similar concerns as Dan, we can consult product about whether it's worth creating an issue for a more complete redesign.
Changing the UI makes it inconsistent with the docs, including the video walkthru. So it's not clear that we want to land lots of little improvements - do we update the docs and video each time? Having product make a conscious decision about whether this is the next update seems cost-effective. |
@sufyaankhan says go. |
305cb84
to
ed60c87
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.
LGTM
refactor: split into components
feat(ui): improve styling
fix: wallet connection and chainStorageWatcher #63 should be merged in first
Still room for improvement, ideally the user shouldn't have to scroll, but I think this looks a little bit better: