Ektron® eWebEditPro Developer's Reference Guide

Manipulating Media File Methods and Properties
• The HTML source page is published in a different directory level from the
directory in which it is edited.
• It is acceptable to have images not appear when a page is being edited.
• You know where the HTML source page is published.
If any condition is not true, you should not use the given resolution type. Instead,
use the local or full resolution type.
Programmatically Accessing Media File Properties
The Media File Object provides access to image properties relating to the file and
the upload process. Values set for these properties affect the operation of the
editor.
”Media File Object” on page 19 lists the properties. You can set default values for
most properties in the configuration data.
This section provides the following topics, which explain how to programmatically
access the image properties under various circumstances.
• Accessing the Media File Object
• Using Netscape to Access Image Properties
• The Entry Point for Using External Scripts
• Setting External Page Parameters
• Changing the Transfer Method on the Fly
• Specifying an Image to Insert
• Modifying the Upload Directory
Accessing the Media File Object
You gain access to the media file object properties programmatically via the
MediaFile method in the eWebEditPro control.
Function getValidExtensions(seditorname)
{
var objMedia = top.opener.eWebEditPro.instances[sEditorName].editor.MediaFile();
return(objMedia.getPropertyString("ValidExtensions"));
}
See Also: “Appendix A: Naming the eWebEditPro Editor” on page 576; ”Media
File Object” on page 19
Using Netscape to Access Image Properties
Within Netscape, the Esker ActiveX plug-in converts the ActiveX control to a plugin
that Netscape can interpret. As a result, you cannot access Media File Object
image properties directly. Instead, use the getProperty and setProperty
methods listed below.
setProperty(strName, strValue)
Ektron® eWebEditPro Developer’s Reference Guide, Release 5.1, Revision 1 425