Takes one parameter, TemplateData
Takes three parameters, Location, Mode, TemplateName
Takes no parameters
Takes no parameters
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
Takes one parameter, Name
Takes one parameter, Name
Takes one parameter, Type
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
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.
Upgrade Notes
In order to Upgrade an existing copy of Moxie.Build V4 or V5 to the most recent version of V5, you can use the Upgrade example files found in the Tools folder to help automate upgrading multi-service systems, or you can just replace the following files/folders: Moxie.exe Moxie.dll Default.dll /DBStore/BuiltIn.* /Lib /Public/BuiltIn /Templates/Admin /Templates/Clean /Templates/Default /Templates/Default5 /Templates/Report
Takes three parameters, Location, ClassNames, AlertText
Has no parameters
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes one parameter, the path of the folder
Takes one parameter, the path where the file is located.
Takes 3 parameters, Location, Mode, Text
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes no parameters
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.
In this example, you will see how to use a public method that works on or with the current WorkQuery that you pass into the method.
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 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.
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.
Has no parameters
Prerequisites: This page assumes that you have already set up your Moxie.Build server and logged in as an admin user. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.
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.
Takes one parameter, a path-mask
Takes two parameters, FolderPath, Action
Has no parameters
Takes a variable number of parameters