-
Notifications
You must be signed in to change notification settings - Fork 778
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
Accounts as tabs #2367
Comments
I really like this. Monero is nearly uniquely positioned to offer the accounts functionality because of on-chain privacy being on by default. I've made use of the accounts feature in the cli for a long time, and wouldn't have it otherwise: it's personal finance 101 to keep stuff separate. I really like the work you guys have been doing, the wallet looks better and better. I'm very appreciative of the fact that we have people like you working on the project. |
Sexy |
Some GUI updates 1 Lets get rid of the left hand side menu’s sub-buttons. Settings button has no sub-buttons in the menu. Instead the buttons are at the top edge of the Settings page. Lets do it this way with Send and Advanced buttons. So sub-buttons to the top edge of each page. And they should be exactly like buttons on Settings page. Horizontally at the top edge of the page. Receive buttons Merchant sub-button has so different functionality than rest of the wallet, that it could look very different than the other buttons and could be located somewhere bottom edge of the Receive page. 2 We could combine the Advanced and the Settings buttons in to one button. That could be called just Settings button. At the top edge of the settings page there would be located horizontally Wallet, Interface, Node, Log, Info, Mining, Prove/check, Shared RingDB and Sign/verify buttons. They could be in one or two rows depending how much there is space. And they really should look like they look now at the Settings page, and be horizontally, because the look so good. 3 The Setting button's written word Settings could be replaced by a cogwheel symbol. Once there is, for a written word, a widely know symbol, it should be used. And remember, less text, more intuitive. The cogwheel symbol could be located at the bottom left corner of the wallet. It would be great to show for a friend or for a noob GUI wallet and say, hey this all you need to know to use wallet, Account, Send and Receive. |
@potatoisfood: Sorry but your comment is mostly off-topic for this issue. |
I would prefer the GUI allows for multiple wallets to be opened instead of simply elevating multiple subaddresses. The tabs should be for different wallets being scanned. This would allow for more consistent real world accounting purposes, while continuing to promote single use addresses. "trading" and "retirement" as only a single distinct subaddress instead of a separate wallet is promoting address re-use which is not a privacy feature. |
Accounts can create as many subaddresses as they want. They promote address re-use the same way as a different wallet file would.
The GUI isn’t built to support multiple wallets so this would require large architectural changes.
This performs way worse than accounts.
Can you explain why “more consistent real world accounting purposes”? Having to save multiple seeds is a worse UX than having multiple accounts in a single seed. |
@Realchacal
your mockup shows them as one in the same? the 'retirement' tab and the 'trading tab' are also address and subaddress 1 and 2 respectively. perhaps I am missing something. in your list of accounts, the column says "first address" of each account. does that mean that there is a tree of subaddresses that the current GUI does not show? |
@1blockologist On the But I see the problem. Showing addresses on the
|
@Realchacal ah I just looked! Thanks for helping me understand that, very amazing! I don't think this concept is adequately conveyed by either of the GUIs, or the team and this affects the UX critiques and possibilities I'll mull it over |
Alternative (more intuitive since the
Accounts
page itself isn't shown as tab):Account
page more intuitive #2312.The text was updated successfully, but these errors were encountered: