Search Results for output

 

[HtmlOutput]

Takes a variable number of parameters

 

Remote

Takes three parameters, Url, InputQuery, OutputQuery

 

Table Report

Table Reports are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As a Report, the Procedure is expected to produce output to be displayed to the user.

 

Record Report

Record Reports are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As a Report, the Procedure is expected to produce output to be displayed to the user.

 

HttpHeader

Takes two parameters, name, value

 

JsonStream$

Used to manipulate a WorkQuery into a JSON type

 

HtmlHistory

Takes two parameters, Title, Path

 

SubTemplate

Takes three parameters, Location, Mode, TemplateName

 

HttpStatus

Takes one parameter, Status

 

Greg$

Takes one parameter, a gregorian number

 

HtmlAlert

Takes three parameters, Location, ClassNames, AlertText

 

Similar%

Takes 2 parameters, pNum1, pNum2

 

Last$

Takes two parameters, Source , Search

 

LastAny$

Takes two parameters, Source , Search

 

Html

Takes 3 parameters, Location, Mode, Text

 

Lang$

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

Similar$

Takes 2 parameters, pString1, pString2

 

HtmlNav

Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn

 

HtmlDropdown

Takes 5 parameters, Location, Mode, Title, Element, Class

 

WithGroup

Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld

 

HtmlNavbar

Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bNotResponsive, bInverted, HtmlPre, HtmlApn

 

NamesToLabels

Takes no parameters

 

HtmlTab

Takes 3 parameters, Location, Mode, bWithNoHeader

 

HtmlRaw

Takes 3 parameters, Location, Mode, bWithNoHeader

 

SaveJsonFile

Takes two parameters, FileName, Options

 

CsvStream

Takes two parameters, CSVData, bNoHeaders

 

TemplateType

Takes one parameter, Type

 

TemplateName

Takes one parameter, Name

 

EnsureNavFields

Takes two parameters, FieldBase, FieldNamesList

 

NameField

Takes three parameters, FieldBase, OldFieldName, NewFieldName

 

JsonStream

Used to manipulate a WorkQuery into a JSON type

 

FixFields

Takes one parameter, a single character

 

Remote Method

A Remote Method may be called by any other Moxie system. It can be used to divide up a large system among a number of backend servers, or as a public API for 3rd parties. In order to call a Remote Method from MOX, the Remote statement is used.

 

Record Action

Record Actions are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As an Action, the Procedure is expected to perform some sort of task, such as an automated set of updates to the Database Record.

 

Public Method

A Public Method may be called from any other Procedure, by the Default plug-in, or a Custom COM DLL. Each Public Method may either use specific Input Parameters, or it may accept an Input Query.

 

Function

A special type of Private Method, called a Private Function, is intended to return a single value or multiple values simultaneously.

 

ForEach

Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]

 

AjaxReply

Has no parameters

 

Overview for PHP Developers

This hands-on experience article is written by an experienced PHP developer, and serves as an overview to help you understand the similarities and differences.

 

Learn More about Frontend Development

Prerequisites: This tutorial assumes that you have already set up a Category and Procedure if necessary. This page covers some of the basics that are involved in Front End development using the MOX language.

 

 

Message Handler

A Message Handler is only ever called by the Database on a Database Event. These Event Messages allow a Developer to intercept operations taking place on a per-record level and implement Event based business logic.

 

Table Action

Table Actions are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As an Action, the Procedure is expected to perform some sort of task, such as an automated set of updates to the Database Table.

 

Syntax and Builtin Values, Procedures and Code Documentation

The MOX language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.

 

AmPm$

Takes one parameter

 

[WQFieldList]

Has no parameters

 

SaveFile

Takes two parameters, FileName, FileData

 

Greg%

Takes one parameter, a date of the form yyyy-mm-dd

 

DateAmPm$

Takes one parameter, a string containing a date and time

 

CsvStream$

Takes one parameter bNoHeaders and returns the result to an assigned variable

 

NewQuery

Takes 3 parameters, QueryName, SourceQuery, bWork

 

NewEComQuery

Takes one parameter, QueryName

 

LangWith

Has one parameter, a Content.Lang prefix

 

Return

Takes a variable number of parameters.

 

[Pull] List of Fields from another Query

Takes up to three parameters, QueryName, FieldBase, FieldNames

 

ProcECom

Takes one parameter, QueryName