Component Tab Libraries
For a changelog of New UI in general, please review Changelog.
Please note that these are optional features for the 15.0 release, please refer to New UI Adoption for the new UI transition timeline.
The new CET UI has introduced new features and a new look for component tab libraries, helping you to achieve a more consistent look and feel while organizing your content or products in a more logical way. These features can be enabled by setting the facelift parameter to true when creating the Library.
This is a fixed header that is positioned at the top of the extension library, independent of the scrollable area in the toolbox. The extension name, image, and any commonly accessed functions should go into the header.
A helper class is provided to ease the creation of our standard library headers:
This builder can then be passed to the library like so:
Buttons can now be automatically placed in the section header, where help buttons and section specific settings can be located.
To use this feature, first create a section button:
Then add it to the section's limb:
Sections can have subsections under them, which can help with organising a toolbox in a more logical manner.
To use these, just add a SubSectionLimb as a parent to your existing SnapperLimbs.
Similar objects and tools can be grouped together in tool groups. Clicking on these tool groups inserts the currently selected item into the drawing. Users can access the options available or change the currently selected button, by clicking on the bottom right arrow or right clicking on the button.
To use these tool groups, use a ToolGroupLimb as a parent of the buttons you want to be under the tool group:
As described in Spacing & Layout, the extension's component tab space is divided into columns, which can be used to size and place elements.
By default, the system will auto size your buttons such that the images will show at their native resolution. Odds are, your images are not sized exactly to result in a button size that fits the column grid, so explicit hints should be given to the system to override this behaviour. UIHint can be used for this purpose:
Depending on the breadth of the changes required, using a separate code path (to build a Facelift specific library limb tree) for the new features might be required.
Generally, minor changes like updating to the new icon style should not require a limb tree. However, larger changes such as adopting the new features or rearranging the items in the library, will require a new library limb tree to be created.