Ninext project

Hello everyone,

Yesterday,Philip Canonica  reported a bug related to the "onclick" event in the view fields. It was no longer functioning on tablets and phones. This issue has now been fixed. Many thanks to Philip for bringing this problem to our attention.

Since I had two other ongoing changes, I took the opportunity to release them as well:

1 - Added a delay between successive calls to the debug() function. This allows us to determine the time it takes for a loop or formula to execute. It's particularly useful when dealing with lengthy calculation chains. As an example, thanks to this simple option, I was able to identify a poorly written query and reduce the execution time from 20 seconds to 200 milliseconds.

2 - In the table editing window, I changed the color of the tabs in the field list to distinguish them from the selection color of a field. It might be a small change, but again, it enhances both efficiency and clarity.

All of these updates are now live in version 2.1.22 beta.

Hello everyone,

I've just released version 2.1.23.

I've added two features:

1 - Fields operations to duplicate, copy/paste, and delete using shortcut keys directly on the form (in admin mode):

The idea is to easily replicate a field that you've spent time configuring, whether it's in the same table, another table, or even another database.

This function is directly activated if you use the fieldsInspector option in the Ninext initialization settings.

Duplicate: cmd+D (or ctrl+D)

Duplicates the selected field and positions the new field right after it.

Copy/Paste: cmd+C/cmd+V (or ctrl+C/ctrl+V)

Copy the selected field (cmd+C), then select the field after which the new field will be pasted (cmd+V)

Delete: Backspace (or Delete):

Deletes the selected field without having to open the field editor and click the delete button. This is simply a time-saver.

Copying a field from another table:

If Ninext detects that the field comes from another table, it spontaneously offers to add at the header of every script present in the field, a copy of the original script in the form of a comment. This allows for comparing the original script and how Ninox translates it in the new environment of the copied field.

2 - Call Ninox functions directly from an HTML component:
This feature allows for creating interactions and value passing between HTML fields and Ninox dynamically.

function test(message : text) do
    'Ninox text field' := "Good morning " + #{:text return prompt(message, 'nobody')}#
end;
html(---
  <button id='myButton' onclick='ninext.callNinoxFunction("test", this, "what your name ?")'>Push to try it</button>
---)

function test(message : text) do
    'Ninox text field' := "Good morning " + #{:text return prompt(message, 'nobody')}#
end;
html(---
  <button id='myButton' onclick='ninext.callNinoxFunction("test", this, "what your name ?")'>Push to try it</button>
---)

In this example, there are multiple interactions between Ninox and HTML/JavaScript. When the user clicks on the HTML button, the onclick event calls the ninext.CallNinoxFunction with the following parameters: the name of the function in the Ninox script, the HTML field, and one or more additional parameters that will be passed to the Ninox function. Here, only one additional parameter is passed, which is the text 'what your name'.

In the "test" function, we assign to the Ninox field 'Ninox text field' the value returned by the JavaScript prompt function, which takes 'message' as its argument.

I am attaching a sample application. Check out the NinoxCallBack table for the two formulas that return HTML fields that communicate with Ninox functions.

I hope these two features will help you create applications more easily and with custom interfaces that use HTML/JavaScript when necessary and Ninox scripts whenever possible.

Have fun !