Search Results for path

 

LoadRawFile

Takes one parameter, FilePath

 

HtmlAButton

Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, Extra.

 

HtmlButton

Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod

 

HttpSoap$

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

 

Dir$

Takes one parameter, a path-mask

 

FolderExists$

Takes one parameter, the path of the folder

 

Http$

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

 

HtmlHistory

Takes two parameters, Title, Path

 

SendEmail

Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld

 

HtmlUpload

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

 

HtmlSearchBox

Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt

 

HttpCookie

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

 

[Ajax]

Takes 3 parameters, Trigger, DestinationID, Path

 

HtmlForm

Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod

 

FileExists$

Takes one parameter, the path where the file is located.

 

Folders

Takes a single variable, the relative path to the directory from root of project

 

HtmlJButton

Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, Extra.

 

ListFolders

Takes two parameters, FolderPath, bRecursive

 

LoadFile$

Takes one parameter, PathToFile

 

Folder

Takes two parameters, FolderPath, Action

 

SaveCsvFile

Takes one parameter, FilePath

 

[L] Lookup (DB Field Attribute)

Parameter is the database path that is to be looked up in the form of TableName|Alias|FieldName where it may be a specific fixed path or you may use {} to replace one or more of the path components where the value inside the {} is a field name in the current record.

 

LoadJsonFile

Takes one parameter, PathToFile

 

TRON

Takes one parameter, FilePath

 

[L] Lookup (Top Query)

Parameter is the database path that is to be looked up in the form of TableName|Alias|FieldName where it may be a specific fixed path or you may use {} to replace one or more of the path components where the value inside the {} is a field name in the current record.

 

SaveTabFile

Takes two parameters, FileName, bUseHeaders

 

Text

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

 

NewWithAttach

Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld

 

HtmlETable

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

 

Value

Takes four parameters, FieldBase, Destination, Function, IfLenFld

 

LoadTabFile

Takes two parameters, FileName, bHasHeader

 

LoadCsvFile

Takes two parameters, FileName, bHasHeader

 

LoadNulFile

Takes two parameters, FileName, bHasHeader

 

SaveRawFile

Takes two parameters, FileName, bUseHeaders

 

SaveNulFile

Takes two parameters, FileName, bUseHeader

 

ListFiles

Takes 3 parameters, Folder, Filter, bShowImgSize

 

[FieldList]

Parameter is a space separated list of field names to be displayed.

 

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.

 

CFPurge

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

 

[!] Limited Selection List

Parameter is a comma separated list (using CSV rules and not in quotes) of the options made available to the user which are enforced on save. If the Parameter is just the single word Checkbox, then instead of a drop down list with values, the user will be given a single checkbox: If the field is unchecked the value will be blank, and if it is checked the value will be "y". When used with a Top Query in MOX, this will ensure the field value matches one of the options, if not it will throw a run time error.

 

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.

 

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.

 

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.

 

File

Takes 3 parameters, Destination, Action, Source

 

Tcp$

Takes three parameters, ServerName, Port, bSecure, Send

 

UrlEncode$

Takes one parameter, Source

 

HttpStatus

Takes one parameter, Status

 

Lang$

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

Image

Has 4 parameters, FileName, Action, Val1, Val2

 

SaveFile

Takes two parameters, FileName, FileData

 

IsGroupType$

Takes two parameters: Username, GroupTypes