Skip to content
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

Merged
merged 2 commits into from
Feb 5, 2024
Merged

feat: ui improvements #25

merged 2 commits into from
Feb 5, 2024

Conversation

0xpatrickdev
Copy link
Member

@0xpatrickdev 0xpatrickdev commented Dec 29, 2023

Still room for improvement, ideally the user shouldn't have to scroll, but I think this looks a little bit better:

Screenshot 2023-12-29 at 4 51 11 PM Screenshot 2023-12-29 at 4 50 54 PM

Copy link
Member

@dckc dckc left a 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

import { FormEvent, useState } from 'react';
import { stringifyAmountValue } from '@agoric/ui-components';
import scrollIcon from '../assets/scroll.png';
import istIcon from '../assets/IST.png';
Copy link
Member

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?

Copy link
Member Author

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}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My eye very much expects fungibles to be written horizontally: 10 USD. 5 IST.
stacking IST on top of the logo seems awkward.

image

Copy link
Member Author

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.

@dckc
Copy link
Member

dckc commented Dec 30, 2023

ideally the user shouldn't have to scroll

I'd like to see how it looks with the give / want side by side. Is it obvious to you how to do that?

Copy link
Contributor

@samsiegart samsiegart left a 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.

@dckc
Copy link
Member

dckc commented Jan 11, 2024

Approving because it's an improvement.

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.

cc @sufyaankhan @kbennett2000

@dckc
Copy link
Member

dckc commented Jan 24, 2024

... Having product make a conscious decision about whether this is the next update seems cost-effective.

@sufyaankhan says go.

@0xpatrickdev 0xpatrickdev requested review from dckc and removed request for dckc February 3, 2024 17:41
Copy link
Contributor

@samsiegart samsiegart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@0xpatrickdev 0xpatrickdev merged commit 91e461d into main Feb 5, 2024
1 check passed
@0xpatrickdev 0xpatrickdev deleted the pc/ui-add-prettier branch February 5, 2024 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants