Uploaded image for project: 'RichFaces'
  1. RichFaces
  2. RF-5219

dropSupport: typeMapping attribute have wrong description.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.3.0
    • Fix Version/s: 3.3.0
    • Component/s: doc
    • Labels:
      None
    • Environment:

      \trunk\docs\userguide\en\target\docbook\publish\en-US\html\

      Description

      Currently displayed following description: Map between a draggable type and an indicator name on zone. it's defined with the pair (drag type:indicator name))
      In truth, typeMapping accept string in JSON format(

      {key1:value1,key2:value2...}

      ), where key is a dragType and value is a parameter, defined in dropSupport, that will be passed to indicator content. IOW typeMapping allows to customize indicator(depend on dragType) through the parameters, defined in dropSupport.
      For example,
      dropSupport:
      <rich:dropSupport acceptedTypes="text2"
      typeMapping="

      {text2:dragType2,text1:dragType1}

      ">
      <rich:dndParam name="dragType1" value="dragType1"></rich:dndParam>
      <rich:dndParam name="dragType2" value="dragType2"></rich:dndParam>
      </rich:dropSupport>
      dragIndicator:
      <rich:dragIndicator id="indicator">
      <f:facet name="single">
      <f:verbatim>

      {marker}

      <b>

      {dragType1} {dragType2}

      </b>
      </f:verbatim>
      </f:facet>
      </rich:dragIndicator>
      And two dragSupport with dragType equal to "dragType1" and "dragType2" accordingly.
      So, when you drag element with "dragType1" dragSupport to area with dropSupport, you will see dragType1 in indicator content. The same thing for "dragType2"

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                atsebro Alex Tserbo
                Reporter:
                mvitenkov Mikhail Vitenkov
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: