-
Notifications
You must be signed in to change notification settings - Fork 91
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
chore: UbiquityPool UI Update #860
Conversation
i think the best it's to design a new table from ground up, instead of mocking one similar to frax, what you think? @rndquu |
Honestly I am heavily leaning towards making separate NON REACT separate pages per view. I feel like this would greatly simplify the development, at the risk of slightly non matching elements/behaviors across pages (this technically could be remedied with a shared generic stylesheet though!) I haven't worked on this repository for a while so I haven't made any initiative towards this, but I remember that dealing with the UI in the past was incredibly unwieldily. Anyways if you guys are more comfortable to proceed in React for now, then sure; but if I do get a chance to dive into this, there's a high chance I'm going to want to go raw (like in https://github.com/ubiquity/work.ubq.fi/) |
It won't be a frax'es mock but a simple UI enough to mint/redeem Dollars
I like that react is widely used but don't like to choose over 100 hooks for different use cases. It was way simpler in the early days with class components.
We'll finish the Ubiquity pool page with the current stack so that we could test minting and redeeming of Dollar tokens. Raw js/css will eventually bring us to a mess. If you guys have experience with some simple frontend framework then suggestions are welcome. |
the thing is our whole frontend is make of React i think the approach you mention is good draw a simple table that shows minting/redeeming and a calculation and move on to further visual aspects, later on |
We might be able to whip up a quick version of the UI by doing a |
I will open a new PR reflecting changes introduced in the audit |
Resolves #833