-
Notifications
You must be signed in to change notification settings - Fork 78
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
Extension refurbish - scope/specs #758
Comments
My PoV extending Pierre's wors (dont feel bonded on it): View 1 (PopUp - Quick Access):Title
View 2 (Options/Settings):Tab 1 (current view options):
Tab2 (Settings/Configuration):
|
Did some quick sketch of what I had in mind, of course this can be changed, I'm not a UI designer: The list of all chains smoldot is connected to is displayed in alphabetical order. The "gear" is clickable and would bring you to a screen that lets you configure the bootnodes of that "Default chain". I have intentionally not put "Statemine" under "Kusama" even though they're a relay chain <-> parachain couple, because the average Joe who will use the extension doesn't necessarily know the concepts of relay chain and parachain, and it shouldn't matter for him anyway. |
A few questions @tomaka :
Can you put a bit more context to the sketch you made, where does this live in the UI, to me it looks like a pop-up view of the extension where apps are grouped around networks? |
Yes! Users need to be able to know that there's a not-connected network and understand why it's not connected. Of course a network should only be visible either if it's used by an app or if it's a default network.
Here's an example of what a list of bootnodes looks like:
Users should be able to customize this list, adding and removing individual elements. In principle, "ideologically speaking", there shouldn't be any default bootnode, and users would have to configure bootnodes when they install the extension. But that would be very annoying and non-user-friendly, and for that reason we have a default list. The point again is that the bootnodes in a default list aren't special compared to the ones manually entered and are here just for convenience.
Yes! |
While discussing with Goran - my proposal, was to have a grouping of bootnodes (and capability of adding groups) that user would be able to save in the extension and choose which ones to select - meaning:
etc, etc |
I find this a bit overkill. The reason why you need to be able to customize bootnodes are:
Bootnodes aren't something that you change every week or even every month. It's something that you do either once (and only if you're a very technical person), or temporarily in case of emergency. Basically all we want is to give the users the possibility just in case. It doesn't need to be an actual feature. |
The question on my side is strictly UI based, the "default" is one choice in UI, right? As a user you can add a new choice of bootnodes so now you have 2 choices. Can user say I want to select both choices or does one exclude the other, @tomaka from your answer I would say they can use both, I am right? |
What I had in mind is that the user would be presented with one list. The list is initially filled with the default bootnodes, and you can add/remove individual elements from that list. Bootnodes don't need to be grouped into categories or multiple lists or whatnot. There can be only one list per chain and you modify that list. |
OK that's easy from the UI perspective, on the other hand it's very user-unfriendly, basically we are spilling what's under the hood right in the UI. Might not be an obstacle considering the user profile, but Niko's solution is way more elegant, anyways question answered, thanks. |
I'm not saying I'm correct, but that's intentional. We don't want users to think that they actually have to use that. Again, this feature is only either for very technical people or in case of emergency. And even in case of emergency the idea is that the average user would follow the instructions of someone technical. There is no point in having multiple pre-existing lists of bootnodes that the user can switch between, because there is no advantage in leaving bootnodes disabled. |
This can close due to deprecated specs (banned pages) and in favour of #975 |
(Note: From Element's conversation cc @tomaka )
A summary of what should be in the extension's UI, I think:
Note that I'm not saying that the chains should be in a simple vertical list, I'm just saying that we want to show them in some way.
"status" is a bit vague, but includes:
We could eventually also add more information about chain connections, such as the current block number, maybe number of validators, etc. but not on the main screen. This kind of info should IMO be considered as technical details, and the extension is targeted at the average Joe and not at technical people
There's one thing I'm unsure of, which is whether to show relay chain <-> parachain relationships. For example if a website connects to Westmint (a Westend parachain), should the extension UI show that it's a parachain of Westend? IMO relay chain <-> parachain relationships are also technical details that don't need to be shown to the average Joe, but it could be shown as long as it's not confusing if you don't really know what a parachain is.
The text was updated successfully, but these errors were encountered: