@luis I think we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page [but perhaps that is complicated to implement due to the wrapper. i would actually add a top bar to the wrapper in general, for system wide activities]. I agree that hiding it works, and showing a top notification bar would help the user troubleshoot better. On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I think we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page [but perhaps that is complicated to implement due to the wrapper. i would actually add a top bar to the wrapper in general, for system wide activities]. I agree with the recommending of hiding it works, yet trying to make it more prominent if the network needs to change (the current location and a red dot is not always noticeable). On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@dizzypaty I can’t see that Figma file, would love to check it

@luis I agree that we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page - like marko [but perhaps that is complicated to implement due to the wrapper. i would actually add a top bar to the wrapper in general, for system wide activities]. I agree with the recommending of hiding it works, yet trying to make it more prominent if the network needs to change (the current location and a red dot is not always noticeable). On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I agree that we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page - like marko [but perhaps that is complicated to implement due to the wrapper - or is it? i’ve seen the activity panel designs which is an overlay and i guess the help system must be as well. but i would actually add a fixed top bar to the wrapper in general, for system wide activities]. I agree with the recommending of hiding it works, yet trying to make it more prominent if the network needs to change (the current location and a red dot is not always noticeable). On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I agree that we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page - like marko [but perhaps that is complicated to implement due to the wrapper - or is it? i’ve seen the activity panel designs which is an overlay and i guess the help system must be as well. but i would actually add a fixed top bar to the wrapper in general, for system wide activities - plus gives DAO larger space for their logo instead of a circular avatar]. I agree with the recommending of hiding it works, yet trying to make it more prominent if the network needs to change (the current location and a red dot is not always noticeable). On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I agree that we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page - like marko [but perhaps that is complicated to implement due to the wrapper - or is it? i’ve seen the activity panel designs which is an overlay and i guess the help system must be as well. but i would actually add a fixed top bar to the wrapper in general, for system wide activities - plus gives DAO larger space for their logo instead of a circular avatar]. I agree with the recommendation of hiding the status, yet trying to make it more prominent if the network needs to change (the current location and a red dot is not always noticeable). On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I agree that we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page - like marko [but perhaps that is complicated to implement due to the wrapper - or is it? i’ve seen the activity panel designs which is an overlay and i guess the help system must be as well. but i would actually add a fixed top bar to the wrapper in general, for system wide activities - plus gives DAO larger space for their logo instead of a circular avatar, and gives us space for global user identity avatar in top right]. I agree with the recommendation of hiding the status, yet trying to make it more prominent if the network needs to change (the current location and a red dot is not always noticeable). On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I agree with the recommendation of hiding the status, yet trying to make it more prominent if the network needs to change (the current location and a red dot is not always noticeable). On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”. I do usually like this type of warning being a prominent bar at the top of the page - like marko. But perhaps that is complicated to implement due to the wrapper - or is it? i’ve seen the activity panel designs which is an overlay and i guess the help system must be as well. I would actually add a fixed top bar to the wrapper in general, for system wide activities - plus gives DAO larger space for their logo instead of a circular avatar, and gives us space for global user identity avatar in top right.

hey @yalda, just enabled it for public access, you should be able to view it & comment: https://www.figma.com/file/TRyOTNyTIqcqLM9yANDFq2Ia/Network-status?node-id=0:1 😊 Our Figma design files should all be public by default but sometimes we need to double check this setting is on!

Thank you!

Btw, is there a list somewhere of aragon-ui components that are in the pipeline?

like a “tooltip” component, or cross-browser multiline truncation option for textinput etc.

Hey @yalda, no, not yet, but we are going to start working on a UI kit soon. We’ll redo all aragonUI components in Figma and clean up our foundation elements (colour, type, icons, spacing, etc.). So this kit will be up to date and mirror the current implementation. We’ll obviously make this public so all Aragon apps designers/devs can make use of it and help improve it : )

That being said, we have been working on a tooltip & info popover components to provide more contextual info and help messages. Designs are still WIP but we’ll share once consolidated

We can totally add top-level items to the Aragon client @yalda

I would actually add a fixed top bar to the wrapper in general, for system wide activities
Interesting, what do you mean exactly?

I'm curious what the current approach is to coming to consensus on design patterns (like the new icon styles) which impact application developers. Is the general consensus that each development team is on their own and that users should just deal with a hodge podge of icons if they happen to use apps from different vendors, or is there a plan in mind for maintaining consistency across the UI?

@lkngtn Perhaps we can allow the user to customize the app names & icons, and then provide a huge icon set to choose from (to which developers can add their own if they follow specific guidelines), as well as themes.

@dizzypaty regarding: https://github.com/aragon/aragon/pull/750#issuecomment-487581142
Would it be ok to change the order of the elements for medium and small screens? (it would make it easier to implement the final large iteration).
Current order:

• Description
• Source code
• Details
• Installed Instances
• App version
• Warning

Proposed order:

• Description
• Details
• Installed Instances
• Source code
• Package name (?)
• App version
• Warning

ICYMI: https://twitter.com/lililashka/status/1128943241846579200?s=19

👋 Is there a pattern in your upcoming design system for hover and onClick events within rows on Aragon UI table components?

👋 Is there a pattern in your upcoming design system for hover animations and onClick events within rows on Aragon UI table components?

cc @dizzypaty

Hi @jayalaves! Currently we don’t have any hover or pressed states for the rows in the table component because these rows aren’t interactive per se. However, all the elements displayed within the row (except the content itself), do have these states, for example, the address badge or associated actions buttons.

That being said, I’m working on a variation of the standard table component that will allow users click on a table raw to expand it or rather, unfold it. This will be used in the Permissions app and we’re still working on the design specs, usage and behavior.

I hope this helps, but if you have a specific use case in mind, feel free to share it so we can take it into consideration when working on the different table component configurations : )

Hi @jayalaves! Currently we don’t need any hover or pressed states for the rows in the table component because these rows aren’t interactive per se. However, all the elements displayed within the row (except the content itself), do have these states, for example, the address badge or associated actions buttons.

That being said, I’m working on a variation of the standard table component that will allow users to click on a table row to expand it or rather, unfold it. This will be used in the Permissions app and we’re still working on the design specs, usage and behavior.

I hope this helps, but if you have a specific use case in mind, feel free to share it so we can take it into consideration when working on the different table component configurations : )

Hi @dizzypaty 👋 We’re thinking that there might be a couple good use cases for at least hover states for table rows, to enhance the idea that certain items within it are indeed clickable, and would generally make the interface a little bit more interactive.

Thanks for your reply, and I hope the consideration syncs well with your updates :)