Dr George Atkinson

So the reason that the animations/hiding aren't working with the `ResizableStack` is because of the use of css rules to animate the width and hide the panel. The `ResizableStack` uses...

> I imagined that to be something similar to vscode's left bar, where extensions can add a new tab. I like the idea of this but it's not clear yet...

> Just finished reviewing your changes. I'm not too sure about having the `ResizableStackHandle` trait just for handling the `on_drag` function, Unfortunately the trait is required to add methods on...

Suggestion for a change in terminology. Correct me if I'm wrong but the essence of the options seems to come down to whether it's the track that has the information...

Incidentally this is exactly the approach we use in morphorm for what I believe is the same thing (we call it content_size). It's just a method on a `Node` trait...

> The [`Hierarchy`](https://github.com/vizia/morphorm/blob/main/src/hierarchy.rs#L4) and [`Node`]) traits by @geom3trik from Morphorm looks like interesting prior art too. I realised recently that a better approach is to just have the `Node` trait...

> Ah; at first I was confused what purpose a trait for nodes would serve, that example helped me understand. That seems to be using an ECS architecture, and a...

On the subject of supporting multiple layout algorithms, since I know that Morphorm is being looked at as a candidate, this isn't too far away from what Morphorm does with...

> You made me have a look at it. It's really cool (even if the API is a bit clunky at times) but in my small test it doesn't implement...

> It would be nice to also add a ``PressUp`` event which would be for when an action (mouse press, trigger keys etc.) is released on the view. We could...