Description Cameron Bateman 2008-10-22 19:21:49 EDT

Use Case:

1) User gestures to drop a tag on the Web Page Editor (WPE) canvas.
2) User configures the tag to be dropped
3) User accepts the drop.  System creates tag and adds to canvas.

Normally, case 2 involves the System raising a dialog box to collect the configuration.  The IDropCustomizer can be used to raise such a dialog and collect the information.  A separate bug 250145 tracks the a non-breaking API that is required to pass additional context information to the customizer.

We will ADD a new standard data structure called ICustomizationData that can be populated by an IDropCustomizer to handle the following main customization sub-cases:

1) Attributes.  i.e. setting a default value for id in <h:outputText id="foo"/>
2) Parents. i.e. an h:commandButton needs to be inside an h:form.
3) Children and Templates. i.e. dropping h:column's in h:dataTable.

We will ADD new tag creation commands that will take an ICustomizationData, create a customized tag and add it to a target document.

We will NOT ADD any new UI for drop customization.