As we turn on features in ParaView that allow multiple, configurable views in ModelBuilder, we need to decide which widgets should be dockable panel-based views and which should be central views. Our preliminary decision is based on the function of the view:
central views should be focused on presenting the user's document/data while
dockable views should be focused on presenting the application state.
This is consistent with how ParaView is organized: the pipeline, animation, and colormap inspectors provide users with ways to manipulate what data ParaView shows or how it shows the data; while the render view, spreadsheet view, and chart views provide visualizations of the data itself. It is not a perfect fit (e.g., the display and info panels largely present user data) but a good guideline.
The dockable attribute panel is arguably focused on application state (providing a way to alter attributes in an attribute system) rather than on a visualization of the attributes. However, it is sometimes awkward because atttributes exposed in different top-level tabs cannot be simultaneously visually compared — instead one must switch between tabs manuallly. It is desirable to present these individually but might be undesirable to force them into the central view area where tiling can make size adjustments difficult.
It is unclear whether the model tree-view should be a dockable or central view.