dbxapp Knowledge Runtime and IDE
Search Reference

Runtime and IDE

On this page
  1. Why dbxapp is a Runtime IDE
  2. dbx edit Modi
  3. What dbx edit=9 means
  4. RAD workflow
  5. Advantage
  6. Central error log in the admin dashboard

dbxapp is also a RAD system. RAD means here: Functions are quickly assembled from DD/FD, templates, modules, forms and reports without rewriting the entire infrastructure for each list or form.

Why dbxapp is a Runtime IDE

dbxapp can perform many development and maintenance tasks in the ongoing application:

  • Edit templates in the browser.
  • Maintain content pages in the CMS.
  • DD and FD structures.
  • Synchronize tables.
  • Check reports and forms directly in the target context.
  • Set module inclusions in content.
  • Compose admin panels and dashboard areas from module calls.

The Runtime IDE works not only with source code, but also with forms, reports and structural metadata.

Template Editor and dbx edit Expiration

dbx edit Modi

dbx edit controls how much the output is editable or technically visible.

Mode mode Meaning
dbx edit=0 normal output
dbx edit=1 Website is rendered normally, editable areas are marked
dbx edit=2 Extended processing mode for structured processing
dbx edit=9 Runtime IDE/Entwicklermodus for deep processing and diagnosis

Important:

  • With the normal website output, the interpreter must also be dbx edit > 0 running.
  • Only in the template editor itself [modulus=... Markers are not evaluated.
  • The template editor edits the file /tplNot the rendered DOM.

What dbx edit=9 means

dbx edit=9 is the deepest runtime IDE mode. It serves developers and admins who work directly on structure and output.

Typical tasks:

  • Test the template source.
  • locate module areas.
  • DD/FD-Strukturen.
  • Return layout problems to the correct template file.
  • Understand runtime interaction of content, modules and reports.

dbx edit=9 is not intended for normal end users.

RAD workflow

A typical RAD sequence:

DD definieren
-> FD für Formularsicht ergänzen
-> dbxForm oder dbxReport verwenden
-> Template erstellen
-> Modulroute einbauen
-> im Content oder Admin einbinden
-> im dbx_edit-Modus pruefen

Advantage

The developer does not build a new mini-application every time. It combines existing building blocks:

  • DD/FD for structure.
  • dbxDB for data.
  • dbxForm for processing.
  • dbxReport for lists.
  • dbxTPL for expenditure.
  • ajax.js, confirm.js, openWin.js for browser behavior.

As a result, domain logic remains small and the application uniform.

Central error log in the admin dashboard

The admin dashboard handles files/dbxError.log as a authoritative error signal:

  • Once the file exists, the system state is set to MEASURES set.
  • The full protocol appears HTML masked in a vertically magnifiable scroll area.
  • The deletion button removes only those from dbx()->get file dir() delivered file. A file path from request data is not allowed.
  • The Delete URL will be dbx()->action url() produced. As a result, dbxapp automatically supplements and checks the action token.
  • Title, status, confirmation, success and error messages come from dbxAdmin|admin-dashboard-status and are available in German, English and Spanish.
  • After successful deletion, the dashboard state is recalculated. Other warnings, system messages or DD problems remain effective.

The shared file access is in dbxSysMsg. The dashboard and system message report therefore use the same hardwired and verified deletion operation.