>> I have actually started wondering about the overall usefulness of Accordion
>> given that most UIs seem to prefer multiple expander-like behavior.
> As just mentioned in my last email, I see a lot of similarity between the two.
> An Accordion is kind of a managed group of Expanders.
> Consolidating them might be an option.
Possibly. I'd want to see what the consolidated component ("ExpanderGroup"?)
looked like.
>> I am also wondering if SplitPane is really all that useful or if a more
>> generic "Resizer" component might be better. There are a few issues with
>> SplitPane as it stands:
>> - The property names are a bit strange, since they have to accommodate
>> either a horizontal or a vertical orientation.
>> - The layout logic duplicates some of what is already implemented in
>> TablePane.
> Don't forget that it starts with a default size of 0, which has caught
> out myself an others on the mailing list.
That too.
> I think SplitPane represents a well known UI staple, and shouldn't
> just be discarded, but agree that it is a but clunky to use.
Maybe. I think the ability to resize panes is a requirement. An actual
"SplitPane" component may not be.
>> A Resizer component (or "Sash") could potentially provide the resizing
>> capability, and these could be used within different layout containers
>> (primarily BoxPane and TablePane, I would imagine) to create various
>> configurable layouts.
> Yep, that would be a great addition IMO. Far simpler than adding
> mouse controlled resizing to Container or Component I would guess, but
> just as powerful at the slight expense of one more 'wrapper' element
> in BXML.
> Once it becomes established, SplitPane could probably be retired.
Right - that is what I was thinking.
