This page is maintained for older versions of Rapise only. The latest documentation can be found at: https://rapisedoc.inflectra.com
Naming Conventions

Purpose

The Rapise engine and API follow some simple naming conventions.

 

Usage

You will find descriptions of the naming conventions below.  Note: italicized text represents placeholders.

oSeS<xxx> ? public functions for user

oDo<Action> ? action implementations

o_<somevar> and _<somename> ? private functions and objects

og_<varname> ? system global data.

 

Examples

Here are some examples to clarify the above conventions:

oSeS("object") - gets the object named "object"

oDoClick - public action function to click on something

o_mydata - private variable called mydata

og_publicdata - global variable called publicdata