Search Results for mox

 

Download Moxie.Build

‍ Download Free Download of Moxie.Build Delivered as a simple .zip file, so that you can set it up however you like. This approach allows you to custom install many services on one server , or just run it as an app without an install.

Release Notes

All recent changes to Moxie.Build are documented in the Confirmed for Next Release list on our public Trello Board

In order to Upgrade an existing copy of Moxie.Build V4 to the most recent version, you can use our Upgrade system that is designed to help automate 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/Report

 

 

 

 

 

 

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.

 

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.

 

 

 

 

 

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.

 

Moxie.Build for Developers

Moxie.Build Keeps it Simple The full stack in one app, delivered by one company. Coding with the MOX server side scripting language is concise, well structured, and keeps your focus on the data. Use Moxie.Build in your company to pull together resources, centralize data, customize business workflows, and act as a highly accessible web portal for staff and customers alike.

 

Include

An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.

 

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.

 

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.

 

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.

 

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.

 

Message Handler

A Message Handler is only ever called by the Database on a Database Event. These Event Messages allow a Developer to intercept operations taking place on a per-record level and implement Event based business logic.

 

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.

 

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.

 

Partners

‍ Learn how your development shop can build awesome solutions for engaged customers, and get listed as a Moxie.Build Partner on this website.

 

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.

 

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

 

Get Started with Running on localhost

The following video demonstrates how to download Moxie.Build to your workstation, and run it on localhost.

 

Get Started by Making it Your Own

This video demonstrates how to get started with Moxie.Build with basic customization.

 

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

 

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.

 

Plus8Decode$

Takes one parameter, Source

 

ParseCountAny$

Takes two parameters, Source and Match

 

ParseCountAny%

Takes two parameters, Source and Match

 

LongDate$

Takes one parameter, a Date value

 

LoadFile$

Takes one parameter, PathToFile

 

ParseCount$

Takes two parameters, Source and Match

 

ParseCount%

Takes two parameters, Source and Match

 

Plus8Encode$

Takes one parameter, Source

 

Tally%

Takes two parameters, Source, Match

 

SSColNum$

Takes one parameter, Source

 

TallyAny%

Takes two parameters, Source, Match

 

Tally$

Takes two parameters, Source, Match

 

SSColAlpha$

Takes one parameter, Source

 

Replace$

Takes one existing Source value, and two parameters, Search, NewVal

 

HtmlForm

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

 

Right$

Takes two parameters, Source, Value

 

ReplaceAny$

Takes one existing Source value, and two parameters of equal length, SearchVals, NewVals

 

ExtractAny$

Takes two parameters, Source , Search

 

InStr$

Takes two parameters, Source, Match

 

JsonEncode$

Has two parameters: Source, Options

 

Extract$

Takes two parameters, Source, Search

 

InStr%

Takes two parameters, Source, Match

 

Greg$

Takes one parameter, a gregorian number

 

Greg%

Takes one parameter, a date of the form yyyy-mm-dd

 

FieldDef$

Takes one parameter, FieldName

 

Http$

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

 

CFApi$

Takes three parameters Method, URL, Body

 

[WQRecCount]

Has no parameters

 

Left$

Takes two parameters, Source, Value

 

Len$

Takes one parameter, a Source value

 

Len%

Takes one parameter, a Source value

 

LastAny$

Takes two parameters, Source, Search

 

ApplyLang$

Takes one parameter

 

JsonStream$

Has one parameter, Options

 

[WQResult]

Takes either one parameter, ResultValue, or no parameters

 

Lang$

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

HttpCookie

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

 

HtmlUpload

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

 

ETableStream

Takes two parameters, ExcelTableData, Options

 

Offset

Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld

 

HtmlHistory

Takes two parameters, Title, Path

 

Plus8Decode

Takes three parameters, FieldBase, Fields, IfLenFld

 

WebSafe$

Takes one parameter, Source

 

HtmlBlock / End HtmlBlock

Takes two parameters, Location, Mode

 

HtmlAlert

Takes three parameters, Location, ClassNames, AlertText

 

Get

Takes two parameters, TableName, IfLenFld

 

TemplateType

Takes one parameter, Type

 

Build

Takes a variable number of parameters

 

Lookup

Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld

 

TemplateRuntime

Takes one parameter, Name

 

HttpType

Takes one parameter, Type

 

Num

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

 

SubTemplate

Takes three parameters, Location, Mode, TemplateName

 

Raw

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

 

Verify$

Takes two parameters, Source, AllowedCharacters (case sensitive)

 

HtmlDTable

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

 

KeepIfAll

Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]

 

JsonStream

Used to manipulate a WorkQuery into a JSON type

 

KeepFields

Takes two parameters, FieldBase, FieldNamesList

 

KeepIfAny

Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]

 

Math

Takes a variable number of parameters

 

TallyAny$

Takes two parameters, Source, Match

 

LoadRawFile

Takes one parameter, FilePath

 

HtmlETable

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

 

SetIfAll

Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]

 

SetIfAny

Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]

 

Pull

Takes three parameters, QueryName, FieldBase, FieldNames

 

SaveJsonFile

Takes two parameters, FileName, Options

 

Text

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

 

Trim$

Takes two parameters, Source, Search

 

Files

Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld

 

HtmlBlocks / End HtmlBlocks

Takes two parameters, Location, Mode

 

Verify%

Takes two parameters, Source, AllowedCharacters (case sensitive)

 

[WQMessage]

Takes one parameter, Message, or no parameters

 

ForEach

Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]

 

Function

A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.

 

File

Takes 3 parameters, Destination, Action, Source

 

ETableReply

Takes 2 parameters, Result, Status

 

FailIfRecError

Has no parameters

 

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

Takes a variable number of conditional statements

 

Method

Private Method contained within a given procedure.

 

MsgBox

Takes two parameters, Text, Title

 

LangWith

Has one parameter, a Content.Lang prefix

 

If (Not) / Then

Takes a single Field name, with an optional Not operator, followed by the conditional statement

 

IncrKillCount

Has one parameter.

 

Error

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

 

 

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.

 

 

Home

Web Portals & Databases

 

 

Style Guide, Procedures and Code Documentation

In order for source code to be more readily readable across teams, it is recommended that your source code always be styled according to this style guide.

 

Wisebox Solutions Inc.

We empower your customers to take action.

 

Critical

Takes one parameter, the Name of the critical section

 

[DatePicker]

Takes no parameters

 

Templates Documentation

Prerequisites: This tutorial assumes that you have already learned about Managing Files .

 

[AccKey] Keyboard Accelorator Key

Takes one parameter which is the keyboard key which will be used as the Access Key for a given Database Table's field.

*Note: By default, each Field's Access Key will be initialized to the first character of the Field's Label.

 

CloudFlare Integration

CloudFlare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services

 

Using the Backtick `

Some Work Query command parameters can accept a source of either a Work Query Field name or a text literal. Text literals in these cases are prefixed with a backtick ` character.

 

Try / Catch / Finally / End Try

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

 

Trigger

Takes two parameter, URL, InputQuery

 

TRONLog

Takes one parameter, OutputText

 

[CountIf]

Takes one parameter, TestCondition

 

[TQRecCount]

Has no parameters

 

[TQResult]

Takes either one parameter, ResultValue, or no parameters

 

[TQMessage]

Takes one parameter, Message, or no parameters

 

[HtmlOutput]

Takes a variable number of parameters

 

[If] Assignment (Top Query)

Parameter is divided into two parts, the Test and the Result if True. The test comes prior to the keyword of Then and the Result if True comes after.

 

SetKillCount

Takes one parameter, Value

 

Prefix

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

 

ProcECom

Takes one parameter, QueryName

 

PaaS

Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery

 

NewEComQuery

Takes one parameter, QueryName

 

OnError (Continue)

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

 

[Pull] List of Fields from another Query

Takes three parameters, QueryName, FieldBase, FieldNames

 

Return

Takes a variable number of parameters.

 

ServerLog

Takes one parameter, ServerLogText

 

Remote

Takes three parameters, Url, InputQuery, OutputQuery

 

QBox

Takes two parameters, QueryName, Title

 

Rem / EndRem

A type of Prefix which allows the programmer to create Remarks or Comments in their code.