joinmarket-webui
Show Details implemented
Created a basic funtionality for the show details tab
- [x] Implemented the functionality required
- [x] Needs UX changes, @editwentyone sir PING!
- [ ] Code review needed @theborakompanioni
Current Stage:
can you provide me please all the data that can be made visible so I can design something that makes sense for the user?
can you provide me please all the data that can be made visible so I can design something that makes sense for the user?
@theborakompanioni sir, help us here by telling what more information to be displayed to user.
For the time being. I am just displaying the tx id and type of tx, INTERNAL or EXTERNAL
@editwentyone, me and tbk have decided that this is some of the data that we want to display to user:
- destination id: bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh
- wait time: ~42 mins
- Jar: A (with SVG icon)
- State: scheduled/running
Please use this data to make a UI If you have any more questions. Please let me know.
This is the current state of the scheduler details tab.
@0xSaksham sure, let me clarify first, if I understood correctly:
the user open up the "schedule details" to find this information:
in about this "time", the status is "scheduled or running", the funds will arrive into "Jar A" to this address "destination id: bc1…"?
source: destination id: bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh wait time: ~42 mins Jar: A (with SVG icon) State: scheduled/running
in about this "time", the status is "scheduled or running", the funds will arrive into "Jar A" to this address "destination id: bc1…"?
Yes, a small change is that funds will leave from "Jar A" to the address "destination id"
in about this "time", the status is "scheduled or running", the funds will be withdrawn from "Jar A" to this address "destination id: bc1…"?
here is my attempt for the scheduler details , let me know what you think guys @theborakompanioni @0xSaksham
https://www.figma.com/design/kfejZJFlwBywvLEnPEmJo1/JoinMarket-UI?node-id=4409-85658&t=qBOp8hvNNS4X47ZX-11
@theborakompanioni I think it raised some merge conflict to this. Please accept the incoming change to fix it locally.
@theborakompanioni I think it raised some merge conflict to this. Please accept the incoming change to fix it locally.
Can you resolve the conflicts yourself? You can always rebase on devel! :raised_hands:
Can you resolve the conflicts yourself? You can always rebase on
devel! 🙌 Done!
Just duplicate import statements!
@0xSaksham It seems you have an old prettier dependency. Please keep in mind to always do an npm install when branching off of devel. :wink:
@0xSaksham Converted to darft as this seems not finished and reviewable. Undraft whenever you feel it is ready for review! :rocket: