
Dreamweaver architecture 323
Group files
Group files contain a list of participants, and participant files have all server-model-specific
code data. Participant files can be used by more than one extension, so several group files can
refer to the same participant file.
The following example shows a high-level view of the Server Behavior Group EDML file. For
a complete list of elements and attributes, see “Group EDML file tags” on page 340.
<group serverBehavior="Go To Detail Page.htm" dataSource="Recordset.htm">
<groupParticipants selectParticipant="goToDetailPage_attr">
<groupParticipant name="moveTo_declareParam" partType="member"/>
<groupParticipant name="moveTo_keepParams" partType="member"/>
<groupParticipant name="goToDetailPage_attr" partType="identifier" />
</groupParticipants>
</group>
In the groupParticipants block tag, each groupParticipant tag indicates the EDML
participant file that contains the code block to use. The value of the
name attribute is the
participant file name minus the .edml extension (for example, the
moveTo_declareParam
attribute).
Participant files
A participant represents a single code block on the page, such as a server tag, an HTML tag,
or an attribute. A participant file must be listed in a group file to be available to a
Dreamweaver document author. Several group files can use a single participant file.
For example, the moveTo_declareParam.edml file contains the following code:
<participant>
<quickSearch><![CDATA[MM_paramName]]></quickSearch>
<insertText location="aboveHTML+80">
<![CDATA[
<% var MM_paramName = ""; %>
]]>
</insertText>
<searchPatterns whereToSearch="directive">
<searchPattern><![CDATA[/var\s*MM_paramName/]]></searchPattern>
</searchPatterns>
</participant>
Komentarze do niniejszej Instrukcji