Component configuration is very similar to Application Configuration. The main difference is that you're creating objects that others will configure as they're building they're own game. With application customization, the author is defining how the entire application is configured for someone to add their own twist.

An Example: Creating a Flickr Widget

A lot of this is similar to the steps in the Application Configuration page. However, all of the interaction with the customization dialogs happens within the Editor, rather than in the Customizer.

Similar to creating customizable applications, customization of components happens from the Integration menu item in the Advanced section of the Object Builder:



This brings up the Integration Step Management dialog, where you can add, edit, and delete the integration steps.



Clicking on "Add" will let you create new integration steps. The only difference here between Application customization and Component customization is that the "Place Actors" step is invalid in the context of Component customization. In addition, adding integration steps that allow you to modify properties will only provide access to the properties of the component being customized, rather than the entire Application and its children. This is what the editor for the Flickr username property in this component looks like:



You can see that there are a set of instructions that control what happens when the component is consumed by another author, and the correct property being modified is listed.

Once integration is set up for a component, when it is added to a new object by being dragged from the search results, the user will be prompted with a dialog to customize it to their needs:



Once configured, the component should be set up to operate correctly in your application.