Macromedia Dreamweaver 8-extending Dreamweaver
About Macromedia Dreamweaver 8-extending DreamweaverHere you can find all about Macromedia Dreamweaver 8-extending Dreamweaver like manual and other informations. For example: review.
Macromedia Dreamweaver 8-extending Dreamweaver manual (user guide) is ready to download for free.
On the bottom of page users can write a review. If you own a Macromedia Dreamweaver 8-extending Dreamweaver please write about it to help other people. [ Report abuse or wrong photo | Share your Macromedia Dreamweaver 8-extending Dreamweaver photo ]
Manual
Preview of first few manual pages (at low quality). Check before download. Click to enlarge.
Download
(English)Macromedia Dreamweaver 8-extending Dreamweaver, size: 3.5 MB |
Macromedia Dreamweaver 8-extending Dreamweaver
User reviews and opinions
| trycatchthis |
2:27pm on Saturday, October 9th, 2010  |
| Adobe eats rocks. They penalize someone that... I will never buy another Adobe product. I know that this program can be used both on ... | |
| linkworld |
7:01pm on Saturday, July 10th, 2010  |
| Adobe eats rocks. They penalize someone that legally purchases the software and then says oops sorry buy another copy. I know that this program can be used both on various versions of MacOS and Windows. The requirements other than the OS are huge. | |
| woozie |
1:08am on Sunday, April 4th, 2010  |
| Design mode limited, otherwise excellent I have been using Dreamweaver for 5 years now (initially in Macromedia Studio MX). Easier to learn how to hand code I am in my 3rd year of a university degree in Multimedia and Website Development and I have stopped using Dreamweaver... Hard work Somebody asked me the other day if I could get them a copy of Dreamweaver because they wanted to set up their first website. | |
Comments posted on www.ps2netdrivers.net are solely the views and opinions of the people posting them and do not necessarily reflect the views or opinions of us.
Documents
Biography DaniloCelic
SoftwareEngineer, WebAssist.com
ExtendingDreamweaver
DaniloCelic
ExtensiondeveloperforWebAssist.com. TeamMacromediaforDreamweaver. TechnicalEditorforanumberof Dreamweaver,StudioandContributebooks, MXthroughMX2004releases.Contributing authorforDreamweaverMX2004Magic. AuthoratCommunityMX.com
Ideas in motion.
Overview Extensiontypes Wheretomakeyourchanges Documentation,supportforums,books Skillsyouneed Commonextensiontypeswithexamples Packagingitallupfordistribution
CommonExtensionTypes
Commands Objects Behaviors ServerBehaviors Translators Floaters
OtherExtensionTypes
Propertyinspectors Toolbars Menus DataSources Components Reports TagLibraries ServerFormats ServerModels C++DLLsand
SomeAdditionalExtensibilityAreas
Snippets PageDesigns DocumentTypes ThirdPartyTags CodeHints CodeColoring ReferenceContent
SharedLibraries
Configurationfilelocations:PC
C:\ProgramFiles\Macromedia\Dreamweaver
Configurationfilelocations:Mac
HD:Applications:MacromediaDreamweaver
8\Configuration
C:\DocumentsandSettings\UserName\Application
8:Configuration
HD:Users:username:Library:Application
Data\Macromedia\Dreamweaver8\Configuration
C:\DocumentsandSettings\AllUsers\Application
Support:Macromedia:Dreamweaver8:Configuration
HD:private:var:root:Application
Configurationfileprecedence
Usersfolder AllUsers/Rootfolder ApplicationInstallfolder
GettingStartedDocumentation
Help>ExtendingDreamweaver Help>DreamweaverAPIReference Help>ManageExtensions>Help>Creatingand
SubmittingExtensions
LiveDocs livedocs.macromedia.com/dreamweaver/8/ DreamweaverMX2004SDK: tinyurl.com/2x2r4(Macromedia.com) MXIFileFormat tinyurl.com/6v3r9(Macromedia.com)
BooksDedicatedtoExtending
BuildingDreamweaver4andDreamweaver
BooksSomeExtendinginfo
DreamweaverMX2004TheCompleteReference RayWestandTomMuck tommuck.com/books.cfm Dreamweaver8Bible JoeLowrey idest.com/dreamweaver/
UltraDev4Extensions
TomMuckandRayWest basicultradev.com/building_extensions DreamweaverMXExtensions LauraGutman tinyurl.com/2l9dm(Amazon.com) BeyondDreamweaver JosephLowrey idest.com/beyond
SeeWhatothersHaveDone
MacromediaExchange(1000+): macromedia.com/exchange WebAssist: WebAssist.com InterAKT:IterAKTOnline.com ProjectSeven:ProjectSeven.com CartWeaverCartweaver.com ExtensionDeveloperlistings: dwfaq.com/resources/extensions felixone.it/extensions/mext.asp
Mine:tinyurl.com/5rel9(CommunityMX.com) PaulBoon:tinyurl.com/4ed3a(CommunityMX.com) TomMuck:flashremoting.com/notablog SteveNelson:steve.secretagents.com ScottFegette:weblogs.macromedia.com/sfegette
SupportForums
DreamweaverExtensionsForum NNTP:
forums.macromedia.com/macromedia.exchange.extensions.dreamweaver
LeverageExistingSkills
HTML JavaScript XML Flash
Webforum
tinyurl.com/dlycn(Macromedia.com)
ExtensibilityForumNNTPonly
macromedia.com/support/dreamweaver/extend/form
ExtensionUIdoctypes
ThingsyoucantdoinanExtension
Extensiondialog: <!DOCTYPEHTMLSYSTEM"//Macromedia//DWExtension layoutengine5.0//dialog">
<ahref=yourURL>LinkText</a> Instead:
<ahref="#"onMouseDown="alert('hi')">linktext</a> <ahref="#"><imgsrc="logo.gif"border="0" onMouseDown="alert('hi')"></a>
<!DOCTYPEHTMLSYSTEM"//Macromedia//DWExtension layoutengine8.0//dialog">
Propertyinspector <!DOCTYPEHTMLSYSTEM"//Macromedia//DWExtension layoutengine6.0//pi">
JavaApplets document.write() getElementByID()
Floatingpanel <!DOCTYPEHTMLSYSTEM"//Macromedia//DWExtension layoutengine5.0//floater">
Objects
Configuration/Objects/
DemoObject
<!DOCTYPEHTMLSYSTEM"//Macromedia//DWExtension layoutengine5.0//dialog"> <html> <head><title>ButtonTag</title> <script> functionobjectTag(){ return"<button>"+ document.forms[0].myLabel.value+"</button>" } </script> </head><body> <formname="myForm"> <inputtype="text"name="myLabel"> </form> </body> </html>
canInsertObject objectTag
Demo:ButtonTag
Commands
Configuration/Commands canAcceptCommand commandButtons
DemoCommand
<!DOCTYPEHTMLSYSTEM"//Macromedia//DWExtension layoutengine5.0//dialog"> <html> <head> <title>CommandTemplate</title> <script> //StartAPIfunctions functioncanAcceptCommand(){ //Determinesifthecommandcanberun return(dw.getDocumentDOM()!=null) } functioncommandButtons(){ //Anarrayofbuttonsandfunctions varokCmd="runCmd()" varcancelCmd="window.close() returnnewArray("OK",okCmd,"Cancel",cancelCmd) } Continued
Demo:RemoveAllMetaTags
DemoCommand(Cont.)
functionrunCmd(){ vardom=dw.getDocumentDOM() varmetas=dom.getElementsByTagName('META') for(vari=0i<metas.lengthi++){ metas[i].outerHTML='' } alert('Numberofmetatagsremoved:'+metas.length) window.close() } </script> </head> <body> <formname="theForm"></form> </body> </html>
ServerBehaviors
ServerBehaviorBuilder
ShowifUserinRole EmailForm
ShowIfUserInRole(startingcode)
<cfsetAccessLevels=userRolesHere"> <cfifListContains(AccessLevels, Session.MM_UserAuthorization)> </cfif>
Emailform(startingcode)
<cfifNOTStructIsEmpty(form)> <cfsetnewLocation=newPage.cfm"> <cfsetmail_body=""> <cfsetcr=Chr(13)&Chr(10)> <cfloopindex="form_element"list="#form.fieldnames#"> <cfifform[form_element]NEQ""> <cfsetmail_body=mail_body&form_element &":"&form[form_element]&cr> </cfif> </cfloop> <cfmailto=queryName.toEmail from="queryName.fromEmail subject="queryName.subject> #mail_body#</cfmail> <cfifnewLocationNEQ""> <cflocationurl="@@newLocation@@"addtoken="false"> </cfif> </cfif>
ShowifuserinRole EmailForm
AdditionalServerBehaviorControls
tinyurl.com/3j9xd(BasicUltraDev.com) tinyurl.com/652cj(Macromedia.com)
AdvancedInterfaces
Tabs Wizards
Packagingitallup
MXIFileFormat tinyurl.com/6v3r9 *Donot*overwritesystemfiles
Flash
SampleMXIfiles Object Behavior Command ServerBehavior
ObjectMXI
<macromediaextension name="Buttontag"version="1.0.0"type="object" requiresrestart="true"> <authorname="DaniloCelicWebAssist.com"/> <products> <productname="Dreamweaver"version="6"primary="true" /> </products> <description> <![CDATA[Thisobejctinsertsa<button>tagwitha userspecifiedlabel.]]> </description> <uiaccess> <![CDATA[ThisobjectisfoundontheCommontabofthe InsertBar,andinsertsa<button>tag.]]> </uiaccess>
<files> <filesource="Objects/Common/ButtonTag.html" destination="$dreamweaver/Configuration/Objects/Common "winextension="htm"/> <filesource="Objects/Common/ButtonTag.gif" destination="$dreamweaver/Configuration/Objects/Common "winextension="js"/> </files> <configurationschanges> <insertbarchanges> <insertbariteminsertappendTo="DW_Insertbar_Common"> <buttonfile="Common\ButtonTag.html" id="DW_Insertbar_Common_Button_Tag" image="Common\ButtonTag.gif"/> </insertbariteminsert> </insertbarchanges> </configurationschanges> </macromediaextension>
Packagingitallup(automated)
MXIFileCreator
muzakdeezign.com/mxi_creator/
Questions?
MXIWizard
linecraft.com/products.php
WebAssistDemo
HappyExtending
Wildcard with escape character
Optional whitespace \s*
Required whitespace
Escape characters
The following is a list of escape characters that Dreamweaver supports, along with the strings to specify them and descriptions of their usage.
Escape character
Backslash
The backslash character (\) is the code coloring escape character, so it must be escaped to be specified in a code coloring rule. This escape character matches any non-visible characters, except those listed that match the Newline escape character, such as space and tab characters. The optional white space and required white space wildcards match both the white space and newline characters. This escape character matches the newline (also known as linefeed) and carriage-return characters.
White space
Newline
Maximum string length
The maximum length allowed for a data string is 100 characters. For example, the following blockEnd tag contains a wildcard character.
<blockEnd><![CDATA[<!--\s*#BeginEditable\s*"\*"\s*-->]]></blockEnd>
Assuming the optional white space wildcard strings (\s*) are a single space character, which Dreamweaver generates automatically, then the data string is 26 characters long, plus a wildcard string (\*) for the name.
<!-- #BeginEditable "\*" -->
This leaves an editable region name that can be as man y as 74 characters, which is the maximum of 100 characters minus 26.
Scheme precedence
Dreamweaver uses the following algorithm to color text syntax in Code view:
Dreamweaver determines the initial syntax scheme based on the document type of the current file. The file document type is matched against the scheme.documentType attribute. If no match is found, the scheme where scheme.documentType = "Text" is used. Schemes can be nested if they specify blockStartblockEnd pairs. All nestable schemes that have the current file extension listed in one of the blockStart.doctypes attribute are enabled for the current file and all others are disabled.
All blockStart/blockEnd combinations should be unique.
Schemes can nest within another scheme only if the scheme.priority is equal to or greater than the outer scheme. If the priority is equal, the scheme can nest only in the body state of the outer scheme. For example, the <script>.</script> block can nest only inside the <html>.</html> block where tags are legalnot inside a tag, attribute, string, comment, and so on. Schemes with a higher priority than the outer scheme can nest almost anywhere within the outer scheme. For example, in addition to nesting in the body state of the <html>.</html> block, the <%.%> block can also nest inside a tag, attribute, string, comment, and so on. The maximum nesting level is 4.
Code validation
When opening a document in Code view, Dreamweaver automatically validates that the document is not using any tags, attributes, CSS properties, or CSS values that are not available in the target browsers that the user selected. Dreamweaver underlines errors with a wavy red line. Dreamweaver stores browser profiles in the Browser Profile folder inside the Dreamweaver Configuration folder. Each browser profile is defined as a text file that is named for the browser. For example, the browser profile for Internet Explorer version 6.0 is Internet_Explorer_6.0.txt. To support target browser checking for CSS, Dreamweaver stores CSS profile information for a browser in an XML file whose name corresponds to the browser profile but with a suffix of _CSS.xml. For example, the CSS profile for Internet Explorer 6.0 is Internet_Explorer_6.0_CSS.xml. You might want to make changes to a CSS profile file if you find that Dreamweaver is reporting an error that you do not want. The CSS profile file consists of three XML tags: css-support, property, and value. The following sections describe these tags.
<css-support>
This tag is the root node for a set of property and value tags that are supported by a particular browser.
The property and value tags.
</css-support>
<property>
Defines a supported CSS property for the browser profile.
name, names, supportlevel, message
name="property_name"
The name of the property for which you are specifying support.
names="property_name, property_name,." A comma-separated list of property names for which you are specifying support.
The names attribute is a kind of shorthand. For example, the following names attribute is a shorthand method of defining the name attribute that follows it:
<property names="foo,bar"> <value type="named" name="top"/> <value type="named" name="bottom"/> </property> <property name="foo"> <value type="named" <value type="named" </property> <property name="bar"> <value type="named" <value type="named" </property>
name="top"/> name="bottom"/>
supportlevel="error", "warning", "info",
or "supported" Specifies the level of support for the property. If not specified, "supported" is assumed. If you specify a support level other than "supported" and omit the message attribute, Dreamweaver uses the default message, CSS property name property_name is not supported.
message="message_string"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>My Flash Movie</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head>
Now, save the file as My Flash Movie.htm in the application Configuration/Commands folder (but do not close the file yet). You save the file at this point so you can embed your Flash content with a relative path, otherwise Dreamweaver will try to use an absolute path. Back in the HTML document, between the opening and closing body tags, add an opening and closing form tag. Then, within the form tags, use the Insert > Media > Flash menu option to add your Flash content to the Command definition file. When prompted, select the SWF file in the Commands folder, and click OK. Your Command definition file should now look like the following example (of course, the width and height attributes might differ, depending on your SWF file properties):
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>My Flash Movie</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body> <body> <form> <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/ swflash.cab#version=6,0,29,0" width="200" height="100"> <param name="movie" value="myFlash.swf"> <param name="quality" value="high"> <embed src="myFlash.swf" quality="high" pluginspage="http:// www.macromedia.com/go/getflashplayer" type="application/x-shockwaveflash" width="200" height="100"></embed> </object> </form> </body> </html>
Save the file again. Next, exit and restart Dreamweaver. Select the Command > My Flash Movie menu option, and your Flash content appears in a Dreamweaver dialog box, as shown in the following figure:
This example shows a simple implementation of Dreamweavers Flash content support. After you are familiar with building objects and commands as well as more sophisticated forms, you can integrate Flash content into your Dreamweaver extensions for a more dynamic user experience. For more information, see Chapter 7, Commands, on page 167 about writing a commandButtons() function to add buttons to the dialog box that displays your Flash content.
Insert bar definition tags
The insertbar.xml file contains the following tags and attributes:
<insertbar>
This tag signals the content of the Insert bar definition file. The </insertbar> closing tag specifies the end of the content.
<insertbar> <category id="DW_Insertbar_Common" folder="Common"> <button id="DW_Hyperlink" image="Common\Hyperlink.gif" file="Common\Hyperlink.htm"/>. </insertbar>
<category>
This tag defines a category on the Insert bar (such as Common, Forms, or HTML). The </ category> closing tag specifies the end of the category content.
By default, the Insert bar is organized into categories of use (such as Common, Forms, or HTML). In previous versions of Dreamweaver, the Insert bar was organized similarly by tabs. Users can set their own preferences for how the Insert bar objects are organized (by category or tab). If the user has selected the tab organization, the category tag defines each tab.
N OT E 142
id, {folder}, {showIf}
<category id="DW_Insertbar_Common" folder="Common"> <button id="DW_Hyperlink" image="Common\Hyperlink.gif" file="Common\Hyperlink.htm"/> </category>
<menubutton>
This tag defines a pop-up menu for the Insert bar.
id, image, {showIf}, {name}, {folder}
<menubutton id="DW_ImageMenu" name="Images" image="Common\imagemenu.gif" folder="Images"> <button id="DW_Image" image="Common\Image.gif" enabled="" showIf="" file="Common\Image.htm" /> </menubutton>
<button />
This tag defines a button on the Insert bar that the user clicks to execute the code that the command or file attributes specify.
id, image, name, {canDrag}, {showIf}, {enabled}, {command}, {file}, {tag}, {codeOnly}
<button id="DW_Object" image="Common\Object.gif" name=Object enabled="true" showIf="" file="Common\Obect.htm" />
<checkbutton />
A checkbutton is a button that has a checked or unchecked state. When clicked, a checkbutton appears pressed in and highlighted. When it is unchecked, a checkbutton appears flat. Dreamweaver has Mouse-over, Pressed, Mouse-over-while-pressed, and Disabledwhile-pressed states. The command must ensure that clicking the checkbutton causes its state to change.
Creating the HTML file Adding the JavaScript functions Creating the image Editing the insertbar.xml file Adding a dialog box Building an Insert bar pop-up menu
Creating the HTML file
The title of the object is specified between the opening and closing title tags. You also specify that the scripting language is JavaScript.
To create the HTML file:
Create a new blank file. Add the following code:
<html> <head> <title>Strikethrough</title> <script language="javascript"> </script> </head> <body> </body> </html>
Save the file as Strikethrough.htm in the Configuration/Objects/Text folder.
Adding the JavaScript functions
In this example, the JavaScript functions define the behavior and insert code for the Strikethrough object. You must place all the API functions in the HEAD section of the file. The existing object files, such as Configuration/Objects/Text/Em.htm, follow a similar pattern of functions and comments. The first function the object definition file uses is isDOMRequired(), which tells whether the Design view needs to be synchronized to the existing Code view before execution continues. However, because the Superscript object might be used with many other objects in the Code view, it does not require a forced synchronization.
To add the isDOMRequired() function:
In the HEAD section of the Strikethrough.htm file, between the opening and closing script tags, add the following function:
<script language="javascript"> function isDOMRequired() { // Return false, indicating that this object is available in Code view. return false; } </script>
Next, decide whether to use objectTag() or insertObject() for the next function. The Strikethrough object simply wraps the s tag around the selected text, so it doesnt meet the criteria for using the insertObject() function (see insertObject() on page 162). Within the objectTag() function, use dw.getFocus() to determine whether the Code view is the current view. If the Code view has input focus, the function should wrap the appropriate (uppercase or lowercase) tag around the selected text. If the Design view has input focus, the function can use dom.applyCharacterMarkup() to assign the formatting to the selected text. Remember that this function works only for supported tags (see dom.applyCharacterMarkup() in the Dreamweaver API Reference). For other tags or operations, you may need to use other API functions. After Dreamweaver applies the formatting, it should return the insertion point (cursor) to the document without any messages or prompting. The following procedure shows how the objectTag() function now reads.
The following comment is appropriate for an inspector that is designed to inspect the HAPPY tag:
<!-- tag:HAPPY, priority:8,selection:exact,hline,vline, serverModel:ASP -->
In some cases, you might want to specify that your extension use only Dreamweaver extension rendering (and not the previous rendering engine) by inserting the following line immediately before the tag comment, as shown in the following example:
<!--DOCTYPE HTML SYSTEM -//Macromedia//DWExtension layout-engine 5.0//pi->
The BODY section of a Property inspector file contains an HTML form. Instead of displaying the form contents in a dialog box, however, Dreamweaver uses the form to define the input areas and layout of the Property inspector. The HEAD section of a Property inspector file contains JavaScript functions or a reference to the JavaScript file or files.
How Property inspector files work
At start up, Dreamweaver reads the first line of each HTM and HTML file in the Configuration/Inspectors folder, searching for the comment string that defines the type, priority, and selection type of a Property inspector. Files that do not have this comment as their first line are ignored. When the user makes a selection in Dreamweaver or moves the insertion point to a different location, the following events occur:
Dreamweaver searches for any inspectors that have a within selection type. If there are any within inspectors, Dreamweaver searches up the document tree from the currently selected tag to check whether there are inspectors for any tags that surround the selection. If there are no within inspectors, Dreamweaver searches for any inspectors that have a selection type of exact. For the first tag that has one or more inspectors, Dreamweaver calls each inspectors canInspectSelection() function. If this function returns the value false, Dreamweaver no longer considers the inspector a candidate for inspecting the selection. If more than one potential inspector remains after calling the canInspectSelection() function, Dreamweaver sorts the remaining inspectors by priority. If more than one potential inspector shares the same priority, Dreamweaver selects an inspector alphabetically by name. The selected inspector appears in the Property inspector floating panel. If the Property inspector file defines the displayHelp() function, a small question mark (?) icon appears in the upper-right corner of the inspector. Dreamweaver calls the inspectSelection() function to gather information about the current selection and populate the inspectors fields. Event handlers attached to the fields in the Property inspector interface execute as the user encounters them. (For example, you might have an onBlur event that calls the setAttribute() function to set an attribute to the value that the user enters.)
The following example of the initialPosition() function specifies that the first time the floating panel appears, it should be 420 pixels from the left and 20 pixels from the top in Windows, and 390 pixels from the left side of the screen and 20 pixels from the top of the screen on the Macintosh:
function initialPosition(platform){ var initPos = "420,20"; if (platform == "macintosh"){ initPos = "390,20"; } return initPos; }
initialTabs()
Determines which other floating panels are tabbed together the first time that this floating panel appears. If any listed floating panel has appeared previously, it is not included in the tab group. To ensure that two custom floating panels are tabbed together, each panel should reference the other with the initialTabs() function.
Dreamweaver expects a string of the form
"floaterName1,floaterName2,.floaterNameN".
The following example of the initialTabs() function specifies that the first time the floating panel appears, it should be tabbed with the scriptEditor floating panel:
function initialTabs(){ return "scriptEditor"; }
isATarget()
Dreamweaver MX (Windows only).
Specifies whether other panels can dock to this floating panel. If the isATarget() function is not specified, Dreamweaver prevents other panels from docking to this one. Dreamweaver calls this function when the user tries to combine this panel with others.
Dreamweaver expects a Boolean value: true if other floating panels can dock to this one; false otherwise.
IsATarget() { return true; }
isAvailableInCodeView()
Determines whether the floating panel should be enabled when Code view is selected. If this function is not defined, the floating panel is disabled in the Code view.
Dreamweaver expects a Boolean value: true if the floating panel should be enabled in Code view; false otherwise.
isResizable()
Determines whether a user can resize a floating panel. If the function is not defined or returns a true value, the user can resize the floating panel. If the function returns a false value, the user cannot resize the floating panel.
Dreamweaver expects a Boolean value: true if the user can resize the floating panel; false otherwise.
The following example prevents the user from resizing the floating panel:
function isResizable() { return false; }
selectionChanged()
Called when the floating panel becomes visible and when the selection changes (when focus switches to a new document or when the insertion pointer moves to a new location in the current document). This function should be defined only if the floating panel must track the selection.
<translation whereToSearch="CFLOOP" translationType="tabbed region end">
The custom value is the default case in which no internal Dreamweaver functionality is added to the translation. It is often used when specifying a tag to insert for a custom Property inspector, as shown in the following example:
<translation whereToSearch="directive" translationType="custom">
<openTag>
This optional tag can be inserted at the beginning of the translation section. This tag lets certain other extensions, such as custom Property inspectors, find the translation.
The tagName value is a valid tag name. It should be unique to prevent conflicts with known tag types. For example, if you specify <openTag>MM_DYNAMIC_CONTENT</openTag> the dynamic data is translated to the MM_DYNAMIC_CONTENT tag.
<attributes>
This tag contains a list of attributes to add to the translated tag that is specified by the openTag tag. Alternatively, if the openTag tag is not defined and the searchPattern tag specifies tag, this tag contains a list of translated attributes to add to the tag that is found.
<attribute>
This tag specifies a single attribute (or translated attribute) to add to the translated tag.
attributes
The attributeName="attributeValue" specification sets an attribute to a value. Typically, the attribute name is fixed, and the value contains some parameter references that are extracted by the parameter patterns, as shown in the following example:
<attribute>SOURCE="@@rs@@"</attribute> <attribute>BINDING="@@col@@"</attribute>
<attribute> mmTranslatedValueDynValue="VALUE={@@rs@@.@@col@@}" </attribute>
<display>
This tag is an optional display string that should be inserted in the translation.
The displayString value is any string comprising text and HTML. It can include parameter references that are extracted by the parameter patterns. For example, <display>{@@rs@@.@@col@@}</display> causes the translation to render as {myRecordset.myCol}.
<closeTag>
This optional tag should be inserted at the end of the translated section. This tag enables certain other extensions, such as custom Property inspectors, to find the translation.
The tagName value is a valid tag name; it should match a translation openTag tag.
on the page. Dreamweaver uses a different suffix string to identify include file URLs because not all URL references are translated. Also, only a single URL can be translated as an include file. In resolving a searchPatterns tag, Dreamweaver uses the following algorithm:
Look for the whereToSearch attribute within the searchPatterns tag. If the attribute value starts with tag+, the remaining string is assumed to be the tag name (no spaces are allowed in the tag name).
Look for the limitSearch attribute within the searchPattern tag. If the attribute value starts with attribute+, the remaining string is assumed to be the attribute name (no spaces are allowed in the attribute name).
If these four steps are successful, Dreamweaver assumes a tag/attribute combination. Otherwise, Dreamweaver starts looking for searchPattern tags with a paramName attribute that has a _url suffix and a regular expression that is defined. (For information about regular expressions, see the Regular expressions on page 338.) The following example of a searchPatterns tag has no search pattern because it combines a tag (cfinclude) with an attribute (template) to isolate the URL for dependency file checking, path fixing, and so forth:
<searchPatterns whereToSearch="tag+cfinclude"> <searchPattern paramNames="include_url" limitSearch="attribute+template" /> </searchPatterns>
The tag/attribute combination (see the previous example) does not apply to translation because Dreamweaver always translates to straight text in the JavaScript layer. File dependency checking, path fixing, and so on occurs in the C layer. In the C layer, Dreamweaver internally splits the document into directives (straight text) and tags (parsed into an efficient tree structure).
Updating server behaviors
Replacement update <updatePatterns>
By default, participant EDML files do not have an tag, and instances of the participant are updated in the document by replacing them entirely. When a user edits an existing server behavior and clicks OK, any participant that contains a parameter whose value has changed is removed and reinserted with the new value in the same location. If the user customizes participant code in the document, the participant might not be recognized if the search patterns look for the old code. Shorter search patterns can let the user customize the participant code in their document; however, updating the server behavior instance can cause the participant to be replaced, which loses the custom edits.
<form action="<% my_participant %>">
After deleting the attribute, only form remains.
Using delete flags to limit participant deletion There might be cases where you want to limit the way that participants are deleted. This can be achieved by adding a delete tag to the EDML file. The following example shows a participant that is an href attribute of a link: <a href="<%=MY_URL%>">Link Text</a>
When this attribute participant is deleted, the resulting tag is <a>Link Text</a>, which no longer appears as a link in Dreamweaver. It might be preferable to delete only the attribute value, which is done by adding the following tag to the participant EDML file:
<delete deleteType="innerOnly"/>
Another approach is to remove the entire tag when the attribute is deleted by typing <delete deleteType="tagOnly"/>. The resulting text is Link Text.
Avoiding conflicts with share-in-memory JavaScript files
If several HTML files reference a particular JavaScript file, Dreamweaver loads the JavaScript into a central location where the HTML files can share the same JavaScript source. These files contain the following line:
//SHARE-IN-MEMORY=true
If a JavaScript file has the SHARE-IN-MEMORY directive and an HTML file references it (by using the SCRIPT tag with the SRC attribute), Dreamweaver loads the JavaScript into a memory location where the code is implicitly included in all HTML files thereafter.
Because JavaScript files that are loaded into this central location share memory, the files cannot duplicate any declarations. If a share-in-memory file defines a variable or function and any other JavaScript file defines the same variable or function, a name conflict occurs. When writing new JavaScript files, be aware of these files and their naming conventions.
CHAPTER 16
Data Sources
The Macromedia Dreamweaver 8 Data Sources API functions let you add data sources, which appear in the Plus (+) menu in the Bindings panel (for related information, see the function dreamweaver.dbi.getDataSources() in the Dreamweaver API Reference). Data source files are stored in the Configuration/DataSources/ServerModelName folder. Dreamweaver currently supports the following server models: ASP.Net/C#, ASP.Net/ VisualBasic, ASP/JavaScript, ASP/VBScript, Macromedia ColdFusion, JSP, and PHP/ MySQL. Within each server model subfolder are HTML and EDML files that are associated with the data sources for that server model. The following table lists the files you use to create a data source:
Configuration/DataSources/ ServerModelName
datasourcename.htm
Specifies the name of the data source and where to find the supporting JavaScript files. Defines the code that Dreamweaver inserts into the document to represent the data source value. Contains the JavaScript functions to add, insert, and delete the necessary code into a document.
Configuration/ThirdPartyTags/ Configuration/thirdPartyTags Configuration/Translators/
language.xml language.gif language.htm
Contains information about tags in the markup language. Icon for tags in the language. Contains JavaScript functions for the data translator.
How data translators work
Dreamweaver handles all translator files the same way, regardless of whether they translate entire tags or only attributes. At startup, Dreamweaver reads all the files in the Configuration/ Translators folder and calls the getTranslatorInfo() function to obtain information about the translator. Dreamweaver ignores any file in which the getTranslatorInfo() function does not exist or contains an error that causes it to be undefined.
To prevent JavaScript errors from interfering with startup, errors in any translator file are reported only after all translators are loaded. For more information on debugging translators, see Finding bugs in your translator on page 442.
Dreamweaver also calls the translateMarkup() function in all applicable translator files (as specified in the Translation preferences) whenever the user might add new content or change existing content that needs translation. Dreamweaver calls the translateMarkup() function when the user performs one of the following actions: Opens a file in Dreamweaver Switches back to Design view after making changes in the HTML panel or in Code view Changes the properties of an object in the current document Inserts an object (using either the Objects panel or the Insert menu) Refreshes the current document after making changes to it in another application Applies a template to the document Pastes or drags content into or within the Document window Saves changes to a dependent file Invokes a command, behavior, server behavior, Property inspector, or other extension that sets the innerHTML or outerHTML property of any tag object or the data property of any comment object Selects File > Convert > 3.0 Browser Compatible Selects Modify > Convert > Convert Tables to Layers Selects Modify > Convert > Convert Layers to Tables Changes a tag or attribute in the Quick Tag Editor and presses Tab or Enter
// the conditional statement var trueStart; // The beginning of the true case var falseStart; // The beginning of the false case var trueValue; // The HTML that would render in the true case var attName; // The name of the attribute that is being' // set conditionally. var equalSign; // The position of the equal sign just to the // left of the <#, if there is one var transAtt; // The entire translated attribute var transValue; // The value that must be URL-encoded var back3FromStart; // Three characters back from the start position // (used to find equal sign to the left of <# var tokens; // An array of all the attributes set in the true case var end; // The end of the current conditional statement.
// As long as there's still a <# conditional that hasn't been // translated while (start != -1){ back3FromStart = start-3; end = outStr.indexOf(' #>',start); equalSign = outStr.indexOf('="<# if',back3FromStart); attAndValue = (equalSign != -1)?false:true; trueStart = outStr.indexOf('then', start); falseStart = outStr.indexOf(' else', start); trueValue = outStr.substring(trueStart+5, falseStart); tokens = dreamweaver.getTokens(trueValue,' ');
// If attAndValue is false, find out what attribute you're // translating by backing up from the equal sign to the // first space. The substring between the space and the // equal sign is the attribute. if (!attAndValue){ for (var i=equalSign; i > 0; i--){ if (outStr.charAt(i) == " "){ attName = outStr.substring(i+1,equalSign); break; } }
transValue = attName + '="' + trueValue + '"'; transAtt = ' mmTranslatedValue' + count + '="' + escape(transValue) + '"'; outStr = outStr.substring(0,end+4) + transAtt + outStr.substring(end+4); // If attAndValue is true, and tokens is greater than // 1, then trueValue is a series of attribute/value // pairs, not just one. In that case, each attribute/value // pair must be encoded separately and then added back // together to make the translated value. }else if (tokens.length > 1){ transAtt = ' mmTranslatedValue' + count + '="' for (var j=0; j < tokens.length; j++){ tokens[j] = escape(tokens[j]); if (j>0){ spacer=" "; } transAtt += spacer + tokens[j]; } transAtt += '"'; outStr = outStr.substring(0,end+3) + transAtt + outStr.substring(end+3) // If attAndValue is true and tokens is not greater // than 1, then trueValue is a single attribute/value pair. // This is the simplest case, where all that is necessary is // to encode trueValue. }else{ transValue = trueValue; transAtt = ' mmTranslatedValue' + count + '="' + escape(transValue) + '"'; outStr = outStr.substring(0,end+3) + transAtt + outStr.substring(end+3); } // Increment the counter so that the next instance // of mmTranslatedValue will have a unique name, and // then find the next <# conditional in the code. count++; start = outStr.indexOf('<# if',end); } // Return the translated string. return outStr } function getTranslatorInfo(){ returnArray = new Array(7);
return ""; } // As long as start, which is equal to the location in inStr of the // KENT tag, is not equal to -1 (that is, as long as there is another // KENT tag in the document) while (start != -1){ // Copy everything up to the start of the KENT tag. // This is very important, as translators should never change // anything other than the markup that is to be translated. outStr = inStr.substring(0, start); // Replace the KENT tag with the translated HTML, wrapped in special // locking tags. For more information on the replacement operation, see // the comments in the replaceKentTag() function. outStr = outStr + replCode; // Copy everything after the KENT tag. outStr = outStr + inStr.substring(start+6); // Use the string you just created for the next trip through // the document. This is the most inefficient part of all. inStr = outStr; start = inStr.indexOf('<kent>'); } // When there are no more KENT tags in the document, return outStr. return outStr; } /************************************************************** * The replaceKentTag() function assembles the HTML that will * * replace the KENT tag and the special locking tags that will * * surround the HTML. It calls the getImage() function to * * determine the SRC of the IMG tag. * **************************************************************/ function replaceKentTag(){ // The image to display. var image = getImage(); // The location of the image on the local disk. var depFiles = dreamweaver.getSiteRoot() + image; // The IMG tag that will be inserted between the lock tags. var imgTag = '<IMG SRC="/' + image + '" WIDTH="320" HEIGHT="240" ALT="Kent">\n'; // 1st part of the opening lock tag. The remainder of the tag is assembled below. var start = '<MM:BeginLock translatorClass="DREAMWEAVER_TEAM" type="kent"'; // The closing lock tag. var end = '<MM:EndLock>';
//Assemble the lock tags and the replacement HTML. var replCode = start + ' depFiles="' + depFiles + '"'; replCode = replCode + ' orig="%3Ckent%3E">\n'; replCode = replCode + imgTag; replCode = replCode + end; return replCode; } /****************************************************************** * The getImage() function determines which image to display * * based on the day of the week, the time of day and the * * user's platform. The day and time are figured based on UTC * * time (Greenwich Mean Time) minus 8 hours, which gives * * Pacific Standard Time (PST). No allowance is made for Daylight * * Savings Time in this routine. * ******************************************************************/ function getImage(){ var today = new Date(); // Today's date & time. var day = today.getUTCDay(); // Day of the week in the GMT time zone. // 0=Sunday, 1=Monday, and so on. var hour = today.getUTCHours(); // The current hour in GMT, based on the // 24-hour clock. var SFhour = hour - 8; // The time in San Francisco, based on the // 24-hour clock. var platform = navigator.platform; // User's platform. All Windows machines // are identified by Dreamweaver as "Win32", // all Macs as "MacPPC". var imageRef; // The image reference to be returned. // If SFhour is negative, you have two adjustments to make. // First, subtract one from the day count because it is already the wee // hours of the next day in GMT. Second, add SFhour to 24 to // give a valid hour in the 24-hour clock. if (SFhour < 0){ day = day - 1; // The day count back one would make it negative, and it's Saturday, // so set the count to 6. if (day < 0){ day = 6; } SFhour = SFhour + 24; }
Tags
Primo Gigaset C590 DCR-TRV17K PRS-300 Amplifier NV-VX22EG F-I90HD NW-E505 BC80XLT 26LC42 SPP-A1050 ST-GT350 Siemens A35 GR282MF Playstation 2 XBV713 Expedition-2007 Iway-250C Deskpro EC MX-J300 HQ8240 MB-392AA MA550 DS6211-2 TC7224 30V Date DGB-300BK Quad FM2 Seiko SKA BH-207 KD-G502B WP3892 A5 V101 32LX1D Clp-154 Laptop Plus Hsdpa HX4700 Builder Polaroid A530 Motorola 120E CD850 Maxxum Qtsi KM900 Bizhub C252 HR7775 00 Wizooverb W2 Dvhd 160 CDX-GT111 Yamaha R-5 SU-V98 WD-1025FB EX-Z12 SGH-T746 LN52A550p3F DW4714 Zooreka L1952T-SF Dimage F100 EUF29400W D-160 V2 CU-E9HKE Batterie T4X VC-405N Espio 90MC KAC-646X SGX T2 Finepix E510 DVP620VR-17B Csne9GKE 50PC1DR-UA Assault LA32B530p7R CQ-C1301NE 320MX-2 DMC-ZR1 Boxee BOX Travelmate-5320 Bassproii ASD 12U Turbo-17R Messenger EX-V8 Krypton Review Rising SUN 18 LI PM-A850 Lockstitch Robin R650 Harmony 600 B2240W - 2002 SK50D XRS 9945 SRV-2000 PSC 1355 PL80 RED Edition Pc 7 42PC7DH-UA
manuel d'instructions, Guide de l'utilisateur | Manual de instrucciones, Instrucciones de uso | Bedienungsanleitung, Bedienungsanleitung | Manual de Instruções, guia do usuário | инструкция | návod na použitie, Užívateľská príručka, návod k použití | bruksanvisningen | instrukcja, podręcznik użytkownika | kullanım kılavuzu, Kullanım | kézikönyv, használati útmutató | manuale di istruzioni, istruzioni d'uso | handleiding, gebruikershandleiding
Sitemap
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101