Overview

When implementing EditLive! within an application using the ASP load-time properties provided with EditLive!, it is important to note the scope of the properties once they are set. This section of the documentation details the scope of each load-time property. Properties with a global scope affect all instances of EditLive! within a page, while properties with a local scope affect only the instance of EditLive! they are set for.

Distinguishing Between Local and Global Properties in ASP and ASP.NET

When using either the ASP load-time properties of EditLive!, local and global properties are set in separate objects or tags.

For ASP, global properties are set on the EditLiveForJavaGlobal object while local properties are set via the EditLiveForJava object.

Global Properties

• AutoSubmit Property

• Cookie Property

• DebugLevel Property

• DownloadDirectory Property

• HttpLayerManager Property

• JREDownloadURL Property

• LocalDeployment Property

Note: The Init Method (ASP only) must be called on the EditLiveForJavaGlobal object in the ASP load-time properties in order to load these values for all instances of EditLive! on the page.

Local Properties

• BaseURL Property

• Body Property

• ConfigurationFile Property

• ConfigurationText Property

• Document Property

• Head Property

• Height Property

• Locale Property

• Name Property

• OnInitComplete Property

• Preload Property

• ReturnBodyOnly Property

• Styles Property

• Width Property

Note: The Show Method must be called on the EditLiveForJava object in the ASP load-time properties in order to load these values for the specific instance of EditLive! on the page.