Continued Ecosystem Component Improvements #96

New issue

Closed

opened 2018-06-13 01:34:19 +02:00 by kauffj · 2 comments

kauffj commented

2018-06-13 01:34:19 +02:00

(Migrated from github.com)

Please discuss this ticket with my synchronously, some of this information is better verbally communicated/explained rather than written:

Improve communication of how auxiliary components interact with core components
Allow auxiliary components to be clicked
Add statefulness to the overview (if I expand an area, click a link, and click back, I should be back where I was)
"First class" display of repos

Please discuss this ticket with my synchronously, some of this information is better verbally communicated/explained rather than written: - [ ] Improve communication of how auxiliary components interact with core components - [ ] Allow auxiliary components to be clicked - [ ] Add statefulness to the overview (if I expand an area, click a link, and click back, I should be back where I was) - [ ] "First class" display of repos

kauffj commented

2018-07-05 17:19:39 +02:00

(Migrated from github.com)

@kauffj needs to give feedback on this.

kauffj commented

2018-07-12 16:48:02 +02:00

(Migrated from github.com)

I think this is pretty much there. Some notes:

The auxiliary components show a vertical scrollbar when expanded - intended? If the intent was to keep the height the same as the 3-block stack, they're different heights as well.
Can we try labeling the auxiliary components in the same light gray of the circle prior to expanding one of the 3 blocks? Can we also allow them to be clicked prior to expanding?

I think this is pretty much there. Some notes: - The auxiliary components show a vertical scrollbar when expanded - intended? If the intent was to keep the height the same as the 3-block stack, they're different heights as well. - Can we try labeling the auxiliary components in the same light gray of the circle prior to expanding one of the 3 blocks? Can we also allow them to be clicked prior to expanding?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.tech#96

No description provided.