Search Results for url

 

UrlEncode$

Takes one parameter, Source

 

UrlDecode$

Takes one parameter, Source

 

Remote

Takes three parameters, Url, InputQuery, OutputQuery

 

CFPurge

Takes one parameter, the URL to purge from CloudFlare's cache

 

CFApi$

Takes three parameters Method, URL, Body

 

SaveHttpFile

Takes two parameters, FileName, URL

 

HtmlUpload

Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText

 

HttpCookie

Takes 6 parameters, Name, Value, Path, Domain, Expires, Other

 

Logout

Takes one parameter, SessionID

 

Http$

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

 

HttpSoap$

Takes 8 parameters, ServerName, Port, bSecure, Path, ExtraHttpHeaders, Envelope, ExtraBody, xml

 

HtmlHistory

Takes two parameters, Title, Path

 

EnsureNavFields

Takes two parameters, FieldBase, FieldNamesList

 

HtmlETable

Takes 6 parameters, Location, Mode, Div, Data, Script, Extra

 

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

 

Text

Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld

 

HtmlDropdown

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

 

HtmlDTable

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

 

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 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.

 

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.

 

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.

 

[Ajax]

Takes 3 parameters, Trigger, DestinationID, Path

 

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.

 

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.

 

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.

 

 

Try / Catch / Finally / End Try

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

 

ETableReply

Takes 2 parameters, Result, Status

 

LangWith

Has one parameter, a Content.Lang prefix