Search Results for content

 

Learn More About the Content Management System

Prerequisites: This tutorial assumes that you have already set up your Moxie.Build server and logged in. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.

 

 

[Header] Raw HTML

Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.

 

[Footer] Raw HTML

Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.

 

Http$

Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, [ContentType], [extraHeader], [body], [rtnHeaders]

 

Raw

Takes one parameter, the contents of which are used for the HTTP Reply Body

 

[Raw] Raw HTML

Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.

 

LangWith

Has one parameter, a Content.Lang prefix

 

Include

An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.

 

RecoverHtml$

Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string

 

HtmlBlock / End HtmlBlock

Takes two parameters, Location, Mode

 

RecoverHtmlObj$

Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string

 

Lang$

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

Try / Catch / Finally / End Try

A traditional way to check for hard errors and enable those errors to error softly.

 

ServerLog

Takes one parameter, ServerLogText

 

SetFirst

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

WorkIf

Takes one parameter, FieldName

 

HtmlReset

Has no parameters

 

EnsureNavFields

Takes two parameters, FieldBase, FieldNamesList

 

Build

Takes a variable number of parameters

 

PickFirstField

Takes three parameters, FieldBase, Destination, SourceFields

 

Math

Takes a variable number of parameters

 

SubTemplate

Takes three parameters, Location, Mode, TemplateName

 

HttpNoCache

Has no parameters.

 

HttpHeader

Takes two parameters, name, value

 

Set

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

HttpType

Takes one parameter, Type

 

SetIf

Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right

 

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.

 

HtmlDTable

Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign

 

Style Guide, Procedures and Code Documentation

In order for source code to be more readily readable across teams, it is recommended that your source code always be styled according to this style guide.

 

Privacy Policy

This is our current Privacy Policy, last updated 2016-01-12.

 

Learn More About Managing Files

Prerequisites: This tutorial assumes that you have already set up your Moxie.Build server and logged in. This page covers some of the basics that are involved in managing files and folders in the Moxie.Build system.

 

HtmlNav

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

 

HtmlNavbar

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

 

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.

 

 

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.

 

JoinQuery

Has 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode

 

Include

Takes one parameter, ProcedureName

 

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.

 

HtmlBlocks / End HtmlBlocks

Takes two parameters, Location, Mode

 

HtmlDropdown

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

 

[Sort] (DB Field Attribute)

Used as a Relationship Attribute, the parameter is a space separated list of field names

 

SetLast

Takes four parameters, FieldBase, Destination, Source, IfLenFld