I noticed that for Perspective Camera and 3D shapes, setTranslate() could be used on their Z axis, so does that mean that we use this method to manipulate 3D planes and setLayout() for 2D planes?
Both seem to move the coordinates of my objects on a 3D plane, so is there any reason not to use them interchangeably (apart from it possibly being bad practice)?
Layout properties and Translate properties have different uses and purposes, though they both are used to position nodes. They can be used independently or, occasionally, together.
Translate properties are typically used for:
OR
Group.There are translateX, translateY, and translateZ properties on Node. So translate properties can be used to translate nodes in both 2D and 3D space..
Layout properties are typically used for:
Pane or AnchorPane) or are unmanaged.OR
layoutChildren, and customizing the layout positioning of child nodes using setLayout.If you are using a 2D layout pane that manages the layout of its children (e.g. StackPane, HBox, VBox), then usually you won't explicitly set layout values in your code. Instead, you will let the layout pane manage the layout and set the layout values.
If you did try to set the layout values yourself and then add a node to a managed layout pane, the layout pane will just overwrite any values you set the next time it runs a layout pass. For example, a StackPane with no additional constraints will ensure that all its children are laid out in the center of the pane, regardless of what layout values you try to set on the node.
There is no layoutZ property on Node, only layoutX and layoutY. So defining a 3D layout manager to layout nodes in a 3D space is not supported.
In 3D work, all nodes are generally placed in a Group and positioned using translate rather than layout.
In 2D work, usually, nodes are placed in layout panes that will manage the layout for you without adjusting the translate value. But translation might still be used for some applications, such as animation work. For example, performing a bounce effect in a Mac dock-type control. The activated application icon bounces up and down but the layout positioning of other icons in the dock control does not change. After the bounce effect completes, the activated application icon returns to its original position in the dock.
Translation values don't affect the layout values for the node and the layout panes don't take them into account when calculating the layout positioning for nodes they manage, which is why a bounce effect using translation won't affect the layout of any other sibling nodes in the pane and the node undergoing the animation effect will return to its original layout position once the translate values return to zero.
In 2D work, layout and translation can be used independently or together as the final position of a node is calculated as layout + translation.
You might still use layout in 3D, though it would be less common. You could use it for laying out nodes on a 2D surface that is repositioned in 3D. For example, if you were implementing a 3D VR UI and wanted to show a dialog to the user with some info text, and Confirm and Cancel buttons, you might layout the dialog in 2D on a layout pane, then place the dialog in a Group and locate it in 3D space using translation.
Transition animations such as TranslateTransition and PathTransition, work by modifying translate values rather than layout values, and so can be used in both 2D and 3D work.
Transforms such as Translate and Rotate can also be used in both 2D and 3D. Transforms are applied independently of both translate and layout properties, with the algorithm, as documented in the Node documentation, being:
Cameras such as PerspectiveCamera are nodes, but it only makes sense to apply translations, rotations, and transforms on them, not layout.