Hi Robert, > This requires that a MenuButton always has a text, however a Skin could > exist that does not contain any text node (but only a bitmap, a simple > shape, etc.). AFAIK Skins separate controls from their concrete > representation.
But that's the point of the content graph. A MenuButton with a non-null text _has_ a text. It was set by the application, the fact that a skin chose not to show the text doesn't matter. The skin could also choose to not display the MenuButton.text as a Text node, but instead somehow render that text directly onto its graphic (you wouldn't be able to see that by inspecting the scene graph). The point is: it doesn't matter what the skin does, the content model is what was defined by application logic. > Which means that the abovementioned use case as a tool for UI testing > cannot be executed if any of the UI libraries (ControlsFX comes to mind) > I use does not support this new model. That's true, but the implementation requirement to support custom content models is quite low, so I would expect actively maintained, high-quality libraries to be able to support it after some time. For your testing use case, I would also submit that even if some of the controls you're using don't define their content model, that doesn't make the feature useless for the vast majority of standard controls that you're probably also using.
