> > I think your question is, what class should you use as the base class for > TabSettingsGeneral. Is that correct? If so, the answer is whatever layout > container is most appropriate for that part of your UI. TablePane is pretty > common for TabPane content, but of course you can use any Component. >
Yes. But as I said, I don't like the fact that this way of doing things makes the bxml weirder. I have to know that my root class is a TablePane to make sense of the fact that my markup starts with a <columns> element and then has TablePane.Row elements. Well, I suppose that case might be kind of obvious :-). Or if my root class extends GridPane, I have to know that to understand why there's this weird columnCount attribute on the root element. Or in general what the styles on the root element are referring to. Okay, maybe it wouldn't be a big hurdle in practice. I think I'll stay with the extra level of hierarchy for now for simplicity. Surely there can't be a huge performance penalty.
