XML FOR DOMINO


code element
Example

Example

Represents programming code.

Containment Hierarchy

Contained by: <action>, <agent>, <area>, <actionhotspot>, <appletparameters>, <appletresource>, <button>, <bordercaption>, <column>, <computedtext>, <databasescript>, <embeddedview>, <embeddednavigator>, <field>, <folder>, <form>, <frameset>, <globals>, <imageref>, <javaapplet>, <page>, <pardef>, <picture>, <popup>, <scriptlibrary>, <section>, <sectiontitle>, <subform>, <subformref>, <view>, %link.computed.content;

Contains: %code.types;

Syntax

<!ELEMENT code ( %code.types; )>

Content

%code.types;


Attributes

<!ATTLIST code

event%string;#REQUIRED
for%tokens;#IMPLIED
enabled%boolean;#IMPLIED
>

enabled


event
for
Defined entities for <code> element

The %code.databasescript.lotusscript.or.formula.events; entity lists the types of events that trigger LotusScript or Formula language code through a databasescript. This entity is used in the following entity: %code.lotusscript.or.formula.events;

Syntax:

<!ENTITY % code.databasescript.lotusscript.or.formula.events "querydocumentdelete | querydocumentundelete| postdocumentdelete | querydroptoarchive| postdroptoarchive ">

The %code.events; entity lists the types of events that trigger code execution.

Syntax:

<!ENTITY % code.events "%code.formula.events; | %code.lotusscript.events;| %code.lotusscript.or.formula.events; | %code.javascript.events; ">

The %code.for.tokens; entity lists the keyword token options of the for attribute. These keyword tokens indicate if the code is intended for use on the Web or in the Notes client. You only need to specify this attribute in those events where Lotus Domino Designer enables you to write code that can be triggered in either. The default in such events is web.

Syntax:

<!ENTITY % code.for.tokens "web | client ">

The %code.formula.events; entity lists the different events that trigger formula language code execution. This entity is used in the %code.events; entity.

Syntax:

<!ENTITY % code.formula.events "defaultvalue | inputtranslation | inputvalidation | windowtitle | webqueryopen | webquerysave | hidewhen | value | selection | htmlattributes | htmlhead | htmlbody | targetframe | helprequest | form | alternatehtml | showsinglecategory | label | displayvalue ">

alternatehtml


defaultvalue
displayvalue
form
helprequest
hidewhen
htmlattributes
htmlbody
htmlhead
inputtranslation
inputvalidation
label
selection
showsinglecategory
targetframe
value
webqueryopen
webquerysave
windowtitle
The %code.javascript.events; entity lists the different events that trigger JavaScript code execution. This entity is used in the %code.events; entity.

Syntax:

<!ENTITY % code.javascript.events "onClick | onDblClick | onMouseDown | onMouseUp | onMouseOver | onMouseMove | onMouseOut | onKeyPress | onKeyDown | onKeyUp | onFocus | onBlur | onLoad | onUnload | onSubmit | onReset | onChange | onError | onHelp | onSelect | Queryopen | Queryrecalc | Postrecalc | Querymodechange | Postmodechange | Postsave | Querysend | Postsend | library">

These code events options execute when:

library


onBlur
onChange
onClick
onDblClick
onError
onFocus
onHelp
onKeyDown
onKeyPress
onKeyUp
onLoad
onMouseDown
onMouseMove
onMouseOut
onMouseOver
onMouseUp
onReset
onSelect
onSubmit
onUnload
Postmodechange
Postrecalc
Postsave
Postsend
Querymodechange
Queryopen
Queryrecalc
Querysend
The %code.javascript.sections; entity lists the global sections that apply to the JavaScript events for the object.

Syntax:

<!ENTITY % code.javascript.sections " jsheader ">

jsheader


The %code.lotusscript.events; entity lists the different events that trigger LotusScript code execution. This entity is used in the %code.events; entity.

Syntax:

<!ENTITY % code.lotusscript.events "initialize | terminate | entering | exiting | onchange | objectexecute ">

These code event options execute when:

entering


exiting
initialize
objectexecute
onchange
terminate
The %code.lotusscript.or.formula.events; entity lists the different events that trigger LotusScript or formula language code execution. This entity is included in the %code.events; entity.

Syntax:

<!ENTITY % code.lotusscript.events "action | onhelp | queryopen | queryrecalc | postopen | querymodechange | querysend | postsend | postmodechange | postrecalc | querysave | postsave | queryclose | click | regiondoubleclick | queryopendocument | queryaddtofolder | querydragdrop | querypaste | postdragdrop | postpaste | onload | onunload | onsubmit | queryentryresize | postentryresize | %code.databasescript.lotusscript.or.formula.events; ">

These code event options execute as follows:

action


click
onhelp
onload
onsubmit
onunload
postdragdrop
postentryresize
postmodechange
postopen
postpaste
postrecalc
postsave
postsend
queryaddtofolder
queryclose
querydragdrop
queryentryresize
querymodechange
queryopen
queryopendocument
querypaste
queryrecalc
querysave
querysend
regiondoubleclick
The %code.lotusscript.sections; entity lists the global sections that apply to the LotusScript events for the object.

Syntax:

<!ENTITY % code.lotusscript.sections " options | declarations ">

These section options specify areas where you can write:

declarations


options
The %code.sections; entity lists the types of global sections that apply to the events for the object.

Syntax:

<!ENTITY % code.sections " %code.lotusscript.sections; | %code.javascript.sections; ">

The %code.types; entity represents the coding languages that are supported by Lotus Notes. This entity contains the <formula>, <lotusscript>, <javascript>, <javaproject>, and <simpleaction> elements.

Syntax:

<!ENTITY % code.types " formula | javascript | lousscript | javaproject | simpleaction+ ">

Example
Example
See Also