A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes 6 parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
In this example, we use a plain old Moxie.Build system and compare it to the MEAN Stack equivalent by building two functionally equivalent versions of a fleshed out To Do List Application. Both versions utilize local user authentication, a relational database system and the security measures found in typical production-level applications on the web today.
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
Takes one existing Source value, and two parameters, Search, NewVal
Takes two parameters: Username, GroupTypes
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
Takes 2 parameters, pNum1, pNum2
Takes 2 parameters, pString1, pString2
Takes two parameters, Source, Value
Takes one existing Source value, and two parameters of equal length, SearchVals, NewVals
Takes two parameters, Source, Value
Takes two parameters Command, Options
Takes one parameter, a Source value
Takes one parameter, a Source value
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, Source
Takes two parameters, Source, Search
Takes two parameters, Source, Value
Takes one parameter, a Date value
Has two parameters: Source, Options
Takes two parameters, Source, Values
Has two parameters: Source, Options
Has two parameters: Source, Name
Has one parameter, Options
Takes two parameters, Source, Value
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes two parameters, Data, Options
Takes two parameters, PathToFile, Options
Takes two parameters, Location, Mode
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
Takes two parameters, FileName, Options
Takes two parameters, Source, Value
Takes one parameter, Source
Takes two parameters, Location, Mode
Takes two parameters, Source, Options
Takes two parameters, Source, Value
Takes one parameter, Source
Takes three parameters, TableName, Alias, Password
Takes two parameters, Name, Value
Takes one parameter, a single character
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, name, value
Takes three parameters, Login, Password, bRememberMe
Takes two parameters, Source, Match
Takes a variable number of conditional logical if statements
A set of instructions that can be called with parameters to run in the current scope.
Takes a single parameter, a QueryName
Takes one parameter, the Name of the critical section
Takes three parameters, Destination, Action, Source
Takes one parameter, Control
Takes a variable number of conditional statements to compare against a single source
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Takes two parameters, FileName, FileData
Takes a single string as parameter, which is then appended to each line in the code block.
Takes a variable number of parameters.
This is our current Privacy Policy, last updated 2016-01-12.
This style guide provides comprehensive standards for writing clean, maintainable, and consistent MOX code for Moxie.Build. Code examples on this page are for illustrative purposes and are only intended to demonstrate style conventions.
Developing in Moxie.Build on localhost give you the advantage of working with the template files natively. When working on procedures (MOX code) you need to access that through the Procedures page in the Admin area of a Moxie.Build system, if running the server on localhost or on a remote server. When running on a remote server, you can edit the template files via the Files page in the Admin area.
Moxie.Build supports translating any user-facing text into multiple languages from a single database table. Procedures, templates, and database field metadata all share the same translation store, so a string written once is reusable everywhere.
The MOX coding and programming language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.
Takes two parameters, FileName, FileData
Takes one parameter, the URL to purge from CloudFlare's cache
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.
Brief overview on the file structure and contents under Moxie. The files and folders discussed in this post are those that are essential when upgrading to the most recent version of Moxie.Build , or when troubleshooting server errors.
Takes two parameters, FileName, bHasHeader
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes one parameter, FieldName
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
Takes two parameters, Source , Search
Takes one parameter, Source
Takes one parameter, Source
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Has one parameter
Has no parameters
Takes one parameter, Source
Takes one parameter
Has no parameters
The Setup Table controls aspects that can be changed while the server is running, and is intended to contain both Moxie.Build specific values as well as application specific.
Has no parameters
Takes two parameters, Source , Search
Takes three parameters Method, URL, Body
Takes two parameters, User and Password
Takes one parameter
Takes two parameters, Source, Search
Takes one parameter