Optional settings:
• Restrict upload file size.
  
  
• Specify allowed file types (extensions).
  
  
• Upon upload redirect to a "success page".
  
  
• If the uploaded files are images (JPEG format only) they can be resized and compressed.
  You can specify dimensions and the compression quality of the uploaded images.
  
  
• Thumbnails can be created for each of those images as well.
  You can specify thumbnail prefix, dimensions and the compression quality.

Browser detection toolkit for Dreamweaver has been released today. Customize the appearance and content of your web pages based on your web site visitor’s mobile device, web browser, OS platform or a search engine bot crawling your web site.

With this Dreamweaver extension you can accomplish a few tricks:
• Prevent search engines from indexing portions of your content
• Customize user experience based on browser
• Dynamically link style sheets
• Design GUI to match your target mobile device and more....
  
  
Since the detection is server-based (not through JavaScript), it will work regardless of whether JavaScript is enabled or not.

Update for Export to Excel extension for Dreamweaver

New in version 2.2.0:

• Specify your own cell delimiter character (if not specified Server Behavior will try to guess it based on your locale).
• Specify the character to replace delimiter inside the recordset fields to insure CSV integrity

PHP Form Mail Server Behavior inserts PHP code for sending submitted form data to specified recipient(s).
The code will automatically parse all form fields to include in the message body in the "Field name: Field value" format.

You can use the extension to send different messages to multiple recepients by submitting a single form, compose your message using form fields values and more.

• Sender email - required.
• Recipient email - required.
• Message subject- required.
• Message body header.
• Parsed list of fields in the "Field name: Field value" format.
  The fields will appear in the order they are presented in the form.
  You can specify exceptions i.e. fields excluded from this list, such as Submit, Reset, Captcha, Subject, etc.
• Message body footer.
• Message format (HTML or Plain Text).
• Cc (Carbon copy address).
• Bcc (Blind carbon copy address).
• Success page URL.
• Error page URL.

• Progress monitor (graphic progress bar, number of messages sent and percent done).
• Stop, pause, resume and skip to the next (to continue interrupted cycle) while sending.
• Set automatic delay interval (in minutes) to work around hosting provider limitations.
• Upload images to the server and immediately use them in your message.
• Preview and insert images from your server.
• Use message templates: preview and save them to the server or local hard drive (now also available in Firefox); preview and load templates from the server (in txt, html and php file format).
• Specify Character Encoding.
• Change any message parameter at any time during mailout cycle.

Many would agree that Adobe Spry Framework is one of the most exiting features of Dreamweaver CS 3 and definitely the #1 reason for the upgrade.
Besides the obvious ones it contains many hidden features allowing, for example, to manipulate data or execute almost any server-side code through AJAX.
For the past few months I have been working on the set of extensions to bring those features to the surface. Ladies and gentlemen, introducing Spry Data Utilities Toolkit.

Spry Data Utilities is a set of extensions for developing web applications powered by Adobe Spry framework for AJAX.
Using these tools you can take advantage of built-in Dreamweaver Server Behaviors for implementing AJAX-driven data related tasks (e.g. searching, creating, updating and deleting records), as well as building functionality for executing your own server-side code via AJAX(e.g. sending email or uploading files).
Additional Spry buttons for your Insert panel will provide easier access to the most commonly used Spry Region elements.

Included in the Toolkit:
• Recordset to XML (Dataset to XML for ASP.NET) Server Behavior.
  Generate dynamic XML from your Recordset or Dreamweaver ASP.NET Dataset and reference the page as XML data source for your Spry Data Set or save as a file (e.g. for use as a Design Time feed for your Spry Data Set.
  Compatible with ASP.NET (VB and C#), PHP (MySQL), ColdFusion and ASP (VBScript) Server Models.
  
  
• Spry Server Action object.
  Create, update and delete records using built-in Dreamweaver Server Behaviors or execute your own server side code with Spry Server Action object.
  • Specify a page element that will show while the operation is in progress (e.g. "Contacting server" ).
  • Display browser dialog with the message returned from the server.
  • Refresh a Spry Data Set to reflect on the latest data changes (after deleting, creating or updating a record).
  • In addition you can specify the names of your own "success" and "error" functions.
    
    
• Spry Search object.
  Build AJAX-powered search functionality with Spry Search.
  Specify the page element to display if search returns no results and another one to show when the results are available. To be used with Recordset to XML Server Behavior.
  
  
• Spry Region State objects (Error,Loading,Ready) and Spy XML Data Set Total Records object.
  Select a block of content inside your Spry Region and click the corresponding button on the Spry toolbar to assign to it a region state.
  A collection of error icons and animated progress bar images included for your convenience.
  

An article on creating editable dropdown by yours truly has been posted to the Premium content section on DMX zone.

Times New Roman Arial Verdana Courier Georgia

New article by yours truly has been posted to the Premium content section on DMX zone.
Above is the example of the editable dropdown font picker.

• Cross-browser Add to Favorites behavior
• Two form control behaviors: Submit and Reset HTML form

Obviously the code should pop-up a JavaScript message box. It worked perfectly fine in any modern browser on both PC and Mac. It did work in Opera also, but only when testing the Flash movie locally. When I tested the code on the server it didn’t work as expected, and by this I mean ... nothing happened at all.

It took me a little while to realise what was "causing the problem":
The <param name="allowScriptAccess" value="sameDomain" /> parameter of the <object> tag and ‘allowScriptAccess="sameDomain"’ attribute of the <embed> tag in the HTML file which contains the swf. By default the file is generated by Flash MX 2004 when the movie is published. When a JavaScript function call is triggered by the Flash movie residing on a remote server the Opera Flash plug-in "thinks" the call is made from a different domain, or so it appears. Removing the attribute/ parameter solves the problem immediately. I understand this might be not the best solution, but a better one yet to be found.

Here is the code of the PHP file that is being loaded into Flash as XML:

<menuitems><?
//Define root folder
$maindir = "." ;
$mydir = opendir($maindir) ;

//Get list of folders
while($folder = readdir($mydir)) {
// A folder is anything without an extension (May not always be true e.g. htaccess file)
$f_is = strstr($folder, “.”);
if ($f_is !="") {
continue;
}
//Output opening XML node for the folder
echo "<item title=\"".$folder."\"><images directory=\"photos/".$folder."\">";

//Get list of JPEG images
$imagelist = opendir($folder);

while($image = readdir($imagelist))
{
//If filename contains “.jp” it’s a JPEG
$i_is = strstr(strtolower($image), ".jp");
if ($i_is =="") {
continue;
}
//Write opening tag for an image
echo "<imageNode jpegURL=\"".$image."\" thumbURL=\"".$image."\" title=\"\">";
//Write image name to be used as a comment but strip the extensioin
echo substr($image,0,strpos($image,"."));
echo "</imageNode>";
}
//Close XML nodes
echo "</images></item>";
closedir($imagelist);
}
closedir($mydir);
?>
</menuitems>