-
Notifications
You must be signed in to change notification settings - Fork 973
Basic tab structure #1
Conversation
Obviously still a lot of unhooked parts, but definitely a step towards the right direction. One thing I'd like to see changed before landing is to move the state outside of tabs.js. Ideally we'll have all components with no state inside of them and fully loaded from prop changes. |
State for tab dragging and dropping? We can move that out. It seems like it might be a lot of work to have state in How do we feel about tacking on additional data to each frame? E.g., frames.[n].tabIsDragging|tabIsDraggingOverLeftHalf|tabIsDraggingOverRightHalf |
As silly as it sounds for this case, yes I was hoping that we could have fully referentially transparent components. Please spend a few minutes to read this to see if it might change your mind. I could see doing an exception here leading to doing exceptions elsewhere. The hope would be to change partially or fully to React stateless components which they stated in 0.14 release notes that there would be further performance optimizations related to them. Note that ImmutableComponent doesn't even consider state for detecting changes right now. I don't think it would be that hard to do the state changes in the store, it would just require a single action which can manage each of those 3 states. I won't try to stop you from landing, but I'd like to give stateless components a shot. |
I agree that we should move the state out, just trying to figure out the right place for it :) Should it go into |
hrm not sure I see why, can you explain? Also let me know what you mean by synchronize, might be better for a slack cha if you want higher bandwidth discussion. |
30b24ee
to
772d340
Compare
2a02fb9
to
d07bdf6
Compare
}) | ||
}, | ||
|
||
tabDragDraggingOverLeftHalf: function (frameProps) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if left + right could just be combined into a single action with different params?
OK going to merge this in, feel free to do the follow ups if you agree in an audit. |
mute/unmute audio without activating tab
Fix omnibar update
add metamask icon for disabled content page
No description provided.