Brimbox Logo Brimbox Version 2.3.4 Released


This is the Modules landing page. This is a good reference and starting point for end users, not just programmers. This area details the use and uses of the standard modules.

In Brimbox, whenever you click on a tab or module button, you are entering a module. Modules correspond to codeblocks underneath, but they also correspond to a user view. Brimbox is meant to have modules added onto or subtracted from. That way a programmer can cater to the user, and program functionality that addresses a user’s needs directly.

Since the standard Brimbox interface is made to accommodate the end user, instructions for Brimbox navigation are warranted. For all default “User” modules, and some “Admin” and “Setup” modules Brimbox preserves the last posted, or postback state. In some cases, state is preserved even when switching tabs or modules, this is called hot state. In general, the back button will render the same result as a tab or module switch, unless Brimbox is preserving state through the “hot state” functionality. This is apparent when using the “Input” or “Query Alias” modules. Brimbox will preserve the form on tab or module switch, no need for a button initiated postback.

So in general, the interface functionality works in three ways, preserved state when forms submitted are programmatically preserved through postback, hot state when forms are preserved even when switching tabs or modules, and finally if not programmatically preserved state can be discarded. The back button will generally give you the same result as last preserved or discarded state, however hot state preservation does not occur when using the back button.

User Modules

Superuser Modules (Setup tab)

Admin Modules (Admin tab)

Updated: 2016-09-17