Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Web Design & Development > Adobe Dreamweaver

This chapter is from the book

This chapter is from the book

Automated Import to Template

Again, we're faced with a powerful command that does exactly what we want—except that it does it with only one document at a time. What's clearly needed here is a parallel to the Export XML extension—one that permits the same choices in scope (current document, open documents, selected files in site panel, or entire site) and stores all the HTML documents generated from importing XML files in a single folder. Constructing this extension takes even less time because much of the work (looping through the selected files, for example) has already been done once before. A key point to take away from this section—aside from how to build the function—is how you can leverage work in one extension to make another.

NOTE

To View the completed code, see Listing 4-4 at the end of this section.

Let's start by defining how we expect the new extension, Import XML, to work:

  1. From the Extension dialog box, the user selects which XML files should be included in the operation.

  2. The user also selects a folder to store the generated pages.

  3. When the command executes, the program gathers the URL of each XML file.

  4. The URL is passed to a function that first creates a blank document to hold the template instance and then imports the XML data.

  5. The new file is saved and closed—and the next XML file, if any, is processed.

The process and the Import XML extension are pretty straightforward. Best of all, we have a starting point to jump off from: the Export XML extension. In a situation like this where so much is duplicated from one extension to the next, I typically open the original extension and do a File, Save As to create a new extension. I save the new file in the appropriate Configuration folder; in this case, that would be Commands.

TIP

Remember that Dreamweaver MX now supports multiuser configurations. If you are working with a multiuser-compatible OS (such as Windows 2000 or Mac OS X), the custom extensions need to be saved in the appropriate user/Macromedia/ Dreamweaver MX/ Configuration folder. Extensions for single-user systems are stored in the Programs/Macromedia/ Dreamweaver MX/ Configuration folder (Windows) or in the Applications:Macromedia: Dreamweaver MX: Configuration folder (Macintosh).

Next, I change the title of the extension. The title is displayed in the title bar of the Extension dialog box. Changing the title is a small thing, but I often forget to do it if I don't do it right away. Now we can begin to seriously modify the base extension, starting with the user interface. In this case, we'll take away an element found in Export XML that is not needed in Import XML: the Template drop-down list. For this version of Import XML, it is assumed that all the XML files declared their associated template. Why? The primary reason is that the key API function we will be using, dw.importXMLIntoTemplate(), requires it. It also greatly simplifies our coding.

With the Template drop-down list and its label deleted, the Import XML extension (see Figure 4.4) is ready for user input.

Figure 4.4 Why rebuild when you can duplicate? The Import XML extension is a duplicate of Export XML with one user interface element removed.

I need to make only one small change to code within the doCommand() function of Import XML. In the Export XML extension, the Wildcards variable was set to allow almost every type of Web document extension: .htm, .html, .shtm, .shtml, .asp, .cfm, .cfml, .php, and .php3. For the Import XML extension, the selection needs to be limited to just one file type: .xml.

As before, the main function is separated from the code that takes the user's selection of which files to be processed. Here, that function is named importXML(), whereas in the original extension, it was named exportXML(). Because the user selection code calls the function for each choice of scope potentially made, the easiest way to modify the code is to do a find and replace.

The first line in the importXML() function serves to create a new, blank document:

var theTempDOM = dw.createDocument();

If this is not done, the template instance is loaded onto the current document.

The next bit of code represents one of the real pitfalls of extension programming: incorrect documentation. According to the Extending Dreamweaver manual, the importXMLIntoTemplate() function takes a file URL as its only argument. Unfortunately, that's wrong. Although it does take a URL pointing to an XML file, the string should be formatted as a file path, like this:

D:\fp2dw\newTemp\anotherTest.xml

instead of a file URL, like this:

file:///D|/fp2dw/newTemp/anotherTest.xml

Dreamweaver provides a function in the MMNotes API collection that converts a file URL to a file path. We can use that without including any other JavaScript file:

var theNewURL = MMNotes.localURLToFilePath(theURL);

With our new URL created, we're ready to perform the key operation of importing the XML into a template:

dw.importXMLIntoTemplate(theNewURL);

Now we create a new document name based on the XML filename and save the file. The new name substitutes an .htm extension for the file's original.xml one and incorporates the user-selected path to a folder:

docName = findObject("folder_text").value + theURL.substring(theURL.lastIndexOf("/") + 1,
theURL.length - 4) + ".htm"; res = dw.saveDocument(theTempDOM, docName);

Finally, if the save operation was successful, the document is closed and control passes back to the doCommand() function to get another URL for processing, if necessary.

if (res) {
  dw.closeDocument(theTempDOM);
}
return;

The most common error to watch for when using an extension like this is malformed XML. If you encounter problems, check the XML file by choosing Validate Current Document as XML from the Validation panel.

Listing 4-4 Import XML (04_importXML.mxp)

<html>
<head>
<title>Import XML</title>

<script language="javascript" src="../Shared/Beyond/Scripts/Beyond_Site.js"></script>
<script language="JavaScript" src="../Shared/MM/Scripts/CMN/UI.js
" type="text/JavaScript"></script> <script language='javascript'> //init globals *************************************************** var theSelect = findObject('fileList'); var theWildText = findObject('wildText'); var theXML = ""; //******************** Primary Functions ************************* function commandButtons(){ -return new Array( 'OK', 'doCommand()', 'Cancel', 'window.close()', 'Help',
'getHelp(theHelpFile)') } function importXML(theURL) { var theTempDOM = dw.createDocument(); var theNewURL = MMNotes.localURLToFilePath(theURL); dw.importXMLIntoTemplate(theNewURL); -docName = findObject("folder_text").value + theURL.substring(theURL.lastIndexOf("/")
+ 1, theURL.length - 4) + ".htm"; res = dw.saveDocument(theTempDOM, docName); if (res) { dw.closeDocument(theTempDOM); } return; } function doCommand() { -var selectArray = new Array("currentDoc","openedDocs", "siteSelected","wholeSite"); var theRes = 1 var theWildCards = ".xml" for (var i=0; i<theSelect.options.length; i++){ if (theSelect.options[i].selected){ whichFiles = selectArray[i]; } } switch (whichFiles){ case "currentDoc": urlArray = getCurrentDoc(); if(urlArray){ importXML(urlArray); } break; case "openedDocs": -agree = confirm("This command cannot be undone. Proceed?"); //If it's ok, go if (agree){ openFilesArray = new Array(); //Get the currently opened files openFilesArray = getOpenedDocs(); //Filter them to get just the ones matching extensions urlArray = filterFiles(theWildCards,openFilesArray); for (var i=0; i<openFilesArray.length; i++){ importXML(urlArray[i]); } } else { return; } break; case "siteSelected": var siteFocus,agree; siteSelectedArray = new Array(); writeSiteSelectedArray = new Array(); siteFocus = site.getFocus(); if(siteFocus == "local" || "site map"){ //Ask the user -agree = confirm("This command cannot be undone. Proceed?"); //If it's ok, go if (agree){ -//Get the urls of the files selected inside the //site window siteSelectedArray = site.getSelection(); -if (siteSelectedArray.length == 0 || siteSelectedArray[0].indexOf(".") == -1) { -alert("No files in Site window selected.\nChoose another Generate From option.") return; } //Filter them to get just the matching extensions -urlArray = filterFiles(theWildCards, siteSelectedArray); for (var i=0; i<urlArray.length; i++){ importXML(urlArray[i]); } } else { return; } } else{ alert("This command can affect only local files"); } break; case "wholeSite": var agree; wholeSiteArray = new Array(); writeFilesArray = new Array(); //Ask the user -agree = confirm("This command cannot be undone. Proceed?"); //If it's ok, go if (agree){ -//Get all the urls of files in the site with matching //extensions wholeSiteArray = getWholeSite(); //Filter them to get just the matching extensions urlArray = filterFiles(theWildCards,wholeSiteArray); for (var i=0; i<urlArray.length; i++){ importXML(urlArray[i]); } } else { return; } break; } window.close(); return; } function findFolder() { findObject("folder_text").value = dw.browseForFolderURL(); } function findFile() { findObject("file_text").value = dw.browseForFileURL("select"); } function getTemplateList() { //returns a list of templates in site var theTemplateDir = dw.getSiteRoot() + "Templates/"; var theTemplates = new Array(); -theTemplates = DWfile.listFolder(theTemplateDir + "*.dwt", "files"); if (theTemplates){ loadSelectList(theTemplateList,theTemplates); } } function initUI() { } </script> </head> <body onLoad="initUI()"> <form name="theForm"> <table border="0"> <tr> <td nowrap> <div align="right">Import XML from</div></td> <td nowrap> <select name="fileList" style="width:220px"> <option selected>Current Document</option> <option>All Open Documents</option> <option>Selected Files in Site Window </option> <option>Entire Site</option> </select> </td> </tr> <tr> <td><div align="right">Save In</div></td> -<td><input name="folder_text" type="text" id="folder_text" style="width:155"> -<input type="button" name="Button" value="Browse" onClick="findFolder()"></td> </tr> </table> </form></body> </html>

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Peachpit products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email ask@peachpit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.peachpit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020