Search Results for user

 

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.

 

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.

 

[!] 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.

 

[SearchFieldList]

Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List.

 

CheckPw$

Takes two parameters, the User Alias, and the User PW to check

 

IsGroupType$

Takes two parameters: Username, GroupTypes

 

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.

 

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.

 

Simple To Do App with MEAN Stack Comparison

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.

 

Http$

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

 

ApplyLang$

Takes one parameter

 

Nightly Management Utility

This utility program manages a server install with one or many Moxie.Build services running by taking care of nightly tasks via a scheduled task

 

Lang$

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

HtmlErr

Takes one parameter, ErrMsg

 

SessionIsGroupType$

Takes one parameter, a List of possible group types

 

RecoverHtmlObj$

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

 

Try / Catch / Finally / End Try

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

 

If (Not) / And / Or / ElseIf / End If

Takes a variable number of conditional statements

 

NewEComQuery

Takes one parameter, QueryName

 

[Ensure] Field Exists

Takes a variable number of parameters, a comma separated list of TopQuery variable names

 

Error

Takes one parameter, the text of the error to throw.

 

[Pull] List of Fields from another Query

Takes three parameters, QueryName, FieldBase, FieldNames

 

Thread

Takes a variable number of parameters

 

OnError (Continue)

Used as a scoping keyword, similar to WorkWith/End WorkWith .

 

Prefix

Takes a single string as parameter, which is then appended to each line in the code block.

 

KeepFields

Takes two parameters, FieldBase, FieldNamesList

 

Value

Takes four parameters, FieldBase, Destination, Function, IfLenFld

 

PWHash

Takes three parameters, TableName, Alias, Password

 

EnsureNavFields

Takes two parameters, FieldBase, FieldNamesList

 

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

 

HtmlDropdown

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

 

HtmlForm

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

 

HttpCookie

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

 

HttpNoCache

Has no parameters.

 

HtmlHistory

Takes two parameters, Title, Path

 

HtmlUpload

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

 

Login

Takes three parameters, Login, Password, bRememberMe

 

Logout

Takes one parameter, SessionID

 

Raw

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

 

Children

Takes two parameters, ChildTableName, Mode

 

EmailErr

The email address that will receive any run time errors that a website encounters

 

Terms of Service

This is our current Terms of Service, last updated 2016-01-12.

 

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.

 

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.

 

[DatePicker]

Takes no parameters

 

[R] Readonly

Has no parameters.

 

 

[MaxLen]

Accepts a numeric value as a parameter.

 

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

 

Get Started with Setting up the Development Environment

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.

 

 

Licensing

Moxie.Build, in short, may be used and licensed free of charge for education, development, or non-profit organizations. Whenever it is deployed by government or for-profit organizations to a production environment the license is granted on a subscription basis.

Moxie.Build includes a number of open source components as part of its distribution; each is subject to their own licenses as included with the files for those components.

 

 

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.

 

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

 

PaaS Method

A PaaS Method may be called by any other Moxie system. In order to call a PaaS Method from MOX, the PaaS statement is used.

 

CopyQuery

Takes two parameters, destinationQuery, sourceQuery

 

Soapbox Studios

Effective Websites. Downtown Quality, Small Town Affordability.

 

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.

 

CopyFirst

Takes two parameters, DestinationQuery, SourceQuery