* Yes, they don't need to be public immediately, although they definitely can be as they're nothing more than a "copy" of the layout panes we already have, but packaged without the Node dependency. We would need pretty quickly the Node implementing the Layoutable interface (which opens the path for people writing their own virtual layouts).
One thing I wanted to mention is that these layout classes can probably be static (unless they need to keep some internal state like HBox.tempArray). If I understand the logic, there is no need for the Layoutable interface either, the owner Node is merely delegates layoutChildren() to the corresponding layout class, passing all the necessary information (scale, snap, etc.) In other words, it might be possible to achieve the main goal of code reuse without any changes to the public APIs. The layout classes can be made public later, once matured. What do you think? -andy
