Now that we have the model, let’s figure out what needs to be configured for editors to use the widget. First, an editor should be enabled to recognize the widget when wanting to select one using the widget selection dialog. For this, we’re going to provide a
title, a short
description, and a
thumbnail for it.
Second, regarding the attributes of a widget, some are predestined for being edited in place, while others should be made editable on the widget’s properties dialog. In general, all attributes that don’t require an editor to select something (e.g. a style or a color) and don’t respond to clicks (buttons, tabs, and the like, do) can be conveniently edited in place, first of all
Thus, in the case of our
DisclosureWidget, the button texts should not be made editable directly on the page because, as indicated, the click needed to focus the button for editing one of its texts would trigger the button’s click event. This is why we’ll configure the button texts so that they show up on the properties dialog. Such a configuration of a widget attribute’s editing control to be made available, as well as the widget’s appearance in the selection dialog, can be handed over to Scrivito using