and here I mention the things I encounter while writing that

Your outside perspective is invaluable. It's easy to make bad design decisions when you know the internals. You tend to work around limitations without thinking about it.

@ron What would be a better name for the builder (in place of

fold

)?

Just

titledpane

?

I was thinking of just pane or titledpane

If we used

titlepane

, we could just use the existing

titlepane

builder and remove

fold

. Would that be reasonable?

would we still use content = vbox?

I kinda like that the current builder (accordion.fold) does the making of the titledpane for me

Currently

content = [node]

would work as it is, and we could add special support for plain builders (with a last one wins rule)

It still would, you would just type

titledpane

where you were typing

fold

.

@User uploaded a file: Untitled

yes

(getting ready to go to france for the weekend, loading books on the ereader, what do you mean I expect it to be boring?) (part of the conversation with my wife 😉 )

@User uploaded a file: Untitled

@User uploaded a file:

@ron: How does that look?

@edvin: So, I've run into a strange use case.

@User uploaded a file: Untitled

With the code above, the

TitledPane

will not be expanded, since the op isn't applied to the node till after the node is added to its parent (in

opcr

).

Would running the op on the node before adding it to the parent cause issues?

I could also remove

if (node.isExpanded) expandedPane = node

and instead add

if (parent is Accordion && node is TitledPane && node.isExpanded) parent.expandedPane = node

to

opcr

after the op is invoked, but that feels hackish.

You can see an example in the

feature/deprecate-fold

branch I pushed up.

@edvin nice!

@User uploaded a file:

Thank you! Testing

ViewModel

now

While I was testing this, had a random Rx thought. I think I cracked the

CompositeObservable

and how to allow manipulations to it.

@User uploaded a file: Untitled

Okay this is pretty neat. You are right @edvin, this was a pretty robust solution

I'll be honest, I was skeptical how it would fit into an Rx approach (which really was the motive behind my asks, no surprise haha). But it actually turned out really nicely. I'm glad I got a moment to really do some case studies with this in depth, and sorry I did not do it sooner.