I work with MBOA.dev on stuff like JMP.chat and co-host the Linux Lads and Linux Dev Time podcasts.
Comment by ~amolith on ~singpolyma/soprani.ca
Ideally want it to work both in the dialler when dialler integration is enabled and in Cheogram when dialler integration is disabled. If it already works in dialler, cool, otherwise should look into doing that as well.
Ticket created by ~amolith on ~singpolyma/soprani.ca
I'd like as much coverage in the server as is reasonable so I can bump dependencies and deploy as soon as the suite passes.
Comment by ~amolith on ~singpolyma/soprani.ca
sgx-jmp added by ~amolith on ~singpolyma/soprani.ca
sgx-bwmsgsv2 added by ~amolith on ~singpolyma/soprani.ca
Ticket created by ~amolith on ~singpolyma/soprani.ca
The app only shows the remaining query count per-key in the settings screen. I like that the home screen stays mostly empty, but if the user wants to avoid being left with no queries when they urgently need directions, they have to periodically remember to check that count.
We should proactively warn the user when they have one non-trial key and fewer than X queries left. The dialogue could say something like
Your only valid key has <count> queries remaining. Visit <server-url> to obtain more.
To minimise the chances of them just tapping something to make it go away, keep it short, call out the important bits, and only provide a neutral "Dismiss" button. Give
<count>
a nice background color with a border radius and use standard link styling for the clickable link.10 is an arbitrary number that seems reasonable to warn about. If that one non-trial key hits 5 left, maybe show the dialogue again.
Comment by ~amolith on ~singpolyma/soprani.ca
Comment by ~amolith on ~singpolyma/soprani.ca
~singpolyma
sgx-jmp
does not have generic command pass-through from what I can tell. Should I look into implementing that similarly to how it's done in cheogram? What all should the ticket include?
Comment by ~amolith on ~singpolyma/soprani.ca
~ossguy is this a duplicate of #104?