Installation

This page only concerns the classic version of Ninext (2.3.7, frozen). To install the plugin, see Plugin installation. The two cannot run together in the same database: as long as the classic version is loaded there, the plugin does not start.

Add the Ninext initialisation code

open your database,
click on the administrator button,
in "Options" > "trigger after open", insert the code below ;

GraphiqueCollé-2-1.png

Ninox

var options := {
  badges: true,
  viewEvent: true,
  buttonEvent: true,
  fieldsInspector: true,
  nativeJS: true,
  tableView: true,
  debugTracer: true,
  languages: false,
  helper: true,
  errorsViewer: true,
  codeFinder: true,
  schemaOverview: true,

  autoCloseDialog: false
 };
var res := http("GET", "https://www.ninext.fr/_functions/ninext").result.code;
dialog("Ninext initialization", html(---
<script ninext=''>{ res }; ninext.start({ formatJSON(options) })</script>
---), ["close"]);

Exit and reopen your database

GraphiqueCollé-3-2.png

Your application may need a special operation to accept Ninext. In this case, the panel below will appear:

Send us an e-mail and we'll send you back a special procedure.

Get Ninext Installation Guide

Install an Older Version

To install a previous version of Ninext, simply add the version number to the loading URL. For example, to load version 2.2.0, use the following URL: https://www.ninext.fr/_functions/ninext/ninext-2-2-0.js

Here is the complete code:

Ninox

var options := {
  badges: true,
  viewEvent: true,
  buttonEvent: true,
  fieldsInspector: true,
  nativeJS: true,
  tableView: true,
  debugTracer: true,
  languages: false,
  helper: true,
  errorsViewer: true,
  codeFinder: true,
  schemaOverview: true,

  autoCloseDialog: false
 };
var res := http("GET", "https://www.ninext.fr/_functions/ninext/ninext-2-2-0.js").result.code;
dialog("Ninext initialization", html(---
<script ninext=''>{ res }; ninext.start({ formatJSON(options) })</script>
---), ["close"]);

In this section

UninstallThis is the page the plugin's Ninext Version Conflict window points to: as long as the classic version is loaded by the database's "After Open" trigger, the plugin does not start.