Online documentation - Websydian v6.5 |
Introduction Implementing Other Uses
Jump functions are used to specify a transfer of control from one Card to another Card within the same WML Deck. A Jump from one WML Card to another happens without accessing the HTTP server. Opposed to WAP Event Handler functions which call the HTTP server resulting in the generation of a new WML Deck.
Jump functions are different from WAP Event Handler functions which access the HTTP server resulting in generation of a new WML Deck.
Jump functions are specified for Template generation-purpose only, and the Jump are used by the Card Template Generators to insert go actions to other Cards within the Deck. Jump functions actually need to be generated and built, as they are called during the Deck Template generation process in order to identify the fields in the WebInput variable (see also the Generate and Build Grid Jump Functions section in the Implementing Deck Template Generator Functions page).
The Designing with Grid Actions section explains WAP-design for different situations implementing actions on data in Grid tables. Jump functions may be involved in some of these implementations.
The Template function scoped under Deck Generators specifies Jump functions and WAP Event Handlers shared by all the Cards in a Deck.
See also the Using the Diagram Editor in WAP Development section of the Other Uses of the Deck Generator page.