Nested panes?

[kewaopcode]

I don't see any way to draw a pane inside of another pane, is this even possible? Maybe this is a core idea to avoid nested panes? There is also no nested panes in the example.

[kewaopcode]

I am thinking about the default Elm style composing, storing child's localstate in the parent's localstate and calling child's event handler inside of the parent's one, so the child isn't even declared in the global list of panes. Do you see any problems with this approach?

[kquick]

I did some preliminary investigation into this many months ago and while I don't recall the specifics at the moment, it basically was not going to be very easy due to context that the nesting would impose, so I dropped the effort.

If this is something you are willing to invest effort into, I'd potentially be open to a pull request but I'd want to be cautious of adding more complexity to the API. Let me know if this is something you want to pursue and I will see if I can find the working dir where I was exploring this and if there are any details I can pass along.

[kewaopcode]

Sure, i would like to see everything. I feel like i still didnt get the idea of Panes, so any additional material (codes, notes, etc) about this project would be interesting for me.

[kquick]

I will be out for a couple of days, so I won't be able to respond until mid-next week.

It's often the case where the event management and rendering has global implications for handling in brick that would affect attempts at nesting. A good approach would probably be to start with a sample application that is implemented against the current brick-panes and then look at a modification of that application that would take advantage of this type of nested panes. If you could start by putting together this type of example, that would give a good candidate target to evaluate how these changes would need to occur in the brick-panes library.