Re: Why don't GridPane, HBox, BorderPane, VBox, StackPane have Skins?
ooo_saturn7 at mail.ru
Fri Apr 26 16:23:37 UTC 2019
Hi Kevin, thank you for your answer.
Skin, as I understand, is a visual representation. You write - `The ability to CSS-style a
Pane should be sufficient to do what you want`. So, on one side is a Skin that is a visual
representation, on the other hand we can change visual representation of Pane via CSS.
However, it is odd for Panes to have Skins. There is no logic for me here. For me it is
odd for Panes not to have Skins. Or I understand something wrong.
>Пятница, 26 апреля 2019, 17:46 +03:00 от Kevin Rushforth <kevin.rushforth at oracle.com>:
>Those are layout containers, not UI controls. Given their purpose -- to
>be containers for laying out children -- it would seem odd for them to
>have skins. The ability to CSS-style a Pane should be sufficient to do
>what you want.
>On 4/26/2019 6:13 AM, Alex Sviridov wrote:
>> I am studying JavaFX API and can't understand why GridPane, HBox, BorderPane, VBox, StackPane don't have Skins. According to Skin API doc:
>>> Base class for defining the visual representation of user interface controls by defining a scene graph of nodes to represent the skin. A user interface control is abstracted behind the Skinnable interface.
>> Why do JavaFX developers use skins only for controls, but not for the above panes? I am asking, because these panes also have visual representation. For example, we can set color, they have children which can be placed somehow differently etc. Could anyone explain?
More information about the openjfx-dev