MACROMEDIA DREAMWEAVER MX 2004-EXTENDING DREAMWEAVER Spezifikationen PDF herunterladen (Seite 409)

Components panel files 409

Extensibility lets you add new component types to the panel. There are several general steps

that you need to follow when adding a new component type to the Components panel:

1. Add the component to the list of available component types for the appropriate server

model(s).

2. Add instructions, known as setup steps, which appear as interactive numbered steps, for

setting up the component in the Components panel or in a dialog box (depending on the

extension for which the steps are implemented). Make sure check marks appear next to any

steps the user has completed.

3. List the components of the component type that exist either on the user’s computer or in

the current site only.

4. Create a new component when the user clicks the Plus (+) button in the Components

panel.

In addition, you will probably want to give the user the ability to edit an existing component

and delete a component.

Components panel files

The Configuration/Components folder has a subfolder for each implemented server model.

Component files are stored in the Configuration/Components/server-model/ComponentType

folder. You can add other server models and supporting server extensions (for more

information, see Chapter 19, “Server Models,” on page 423 and Chapter 15, “Server

Behaviors,” on page 321).

To create a custom component that can work in the Components panel:

■ Create an HTML file that identifies the locations of supporting JavaScript and image files.

■ Write the JavaScript to enable the component.

■ Create or identify existing GIF image files to represent the component in the

Components panel.

If you want the component type to appear in a tree control view, you also need to create the

associated optional files and populate the tree control.

You can set a component type to work at the level of an individual web page, to a set of web

pages, or to an entire site. Your JavaScript code must include the logic for component

persistence—for saving itself between sessions and reloading at the start of a new session.

The following example shows a data entry in the file JavaBeansList.xml (to be saved in the

multiuser configuration folder) that defines the component class and its location:

<javabean classname="TestCollection.MusicCollection"

1 2 ... 404 405 406 407 408 409 410 411 412 413 414 ... 503 504

Keine Kommentare

MACROMEDIA DREAMWEAVER MX 2004-EXTENDING DREAMWEAVER Spezifikationen Seite 409