marigold-dev / decookies Goto Github PK

Context

Following #13 and #15 several issues had been created on the different wallets supported by Beacon SDK:

• Temple ✅ with Temple mobile app => madfish-solutions/templewallet-extension#736

• Kukai => kukai-wallet/kukai#400

• Umami => https://gitlab.com/nomadic-labs/umami-wallet/umami/-/issues/720

• Galleo => Cryptonomic/Deployments#76

• Stribe => Seems to work, since it is using AirGap wallet under the hood...

This issue is there to follow the resolution of each Wallet.

Deploy decookie

Backend (inside @marigold-dev/deku)

For the "backend" the contract will be originated manually by myself when we will decide do to it.

Frontend (this repo)

For the frontend, an auto-deploy on a dedicated URL at each commit on main branch (this branch is protected, so each commit on it is fully working and tested before) would be perfect.

An URI containing cookie and deku-c on marigold.dev would be awesome (cc @oteku @d4hines)

Minor issue
It should be temple and bank instead of temples and banks ( or change farm, factory to plurial...)

Tooltips had been introduced in #57 but they are not very beautiful...
Let's rework them to make compliant with our actual theme.

The UI is super nice (well done!) but it's not immediately obvious for the user that they have to connect their wallet, as the button is small and on the left-hand side of the page. Highlighting the button would help.

There are a lot of useless scrollbars...
Here is an example from edge:

• Vertical scrollbar in each cell is useless
• horizontal scrollbar in div is useless

Tooltips on various parts of the UI would be nice. E.g., if you hover over a grandma, a small tooltip that appears quickly enough saying "Hire a grandma who will cook more cookies for you" would be helpful.

When I click on items rapidly, sometimes they get stuck in production forever. For example, it says I've had 1 grandma in interview for the last 10 minutes. I can no longer make grandmas. I suspect that if a request fails, we never reset the state to allow trying again.

Once the player has connected his/her wallet:

• nickname and nodeURI must be disabled
• "connect wallet" button must be changed to "disconnect"

Once the wallet is disconnected:

• config must be erased (node URI, nickname, cookieBaker, wallet, leaderboard, ovens)

Problem

Actual front is basically a div. For now, it is good enough, but as soon as we will add other buildings it will become impossible to see them and mint them.

Goal is to have a design similar to https://orteil.dashnet.org/cookieclicker/, with the list of “buildings” on the right, and scrollable.

Mobile version is not playable, since we cannot connect the wallet:

It seems that Nickname and NodeURI are not dispatched correctly, and then, not available in the state. Which causes the error shown in the screenshot

Apparently the UI can get stuck if you click too much on cookies producers (e.g. grandmas):

Reloading the page solves this but this is a bit frustrating still.

Just opening this so someone tries to reproduce some day. Right now I have no time for this myself though, sorry.

I wanted to see my ranking and didn't know that I would not lose the current page. The UI should either refuse opening the window or we should keep the connection, if possible.

Problem

Actual leader board is not readable.
Goal is to have a dedicated page to display it.

On brave browser, the giant cookie cannot be displayed:

Problem

When resizing the page, nickname and URI fields just disappear under the header...