Ninext project
good evening to all,
I create this post to organize the Ninext project. For those who are new to it, it is composed of several JavaScript modules that allow you to add badges on tabs and buttons, catch selection events on views, execute JavaScript from Ninox script, inspect dependencies between database fields.
This post is here to talk about the project and the procedure for those who would like to implement it in your databases. I would like to take this opportunity to remind you that this is a test project that evolves regularly and I invite you to be cautious and not to use it on commercial databases for the moment.
The sources of the project are available and downloadable on Github.
Thanks to all of you for all your messages of support and for your help to debug and make the project progress a little more every day .
I made the project initiation procedure evolve thanks to the precious help of M. Daaboul who told me that we could use the Ninox dialog box with HTML code. It is no longer necessary to create a window and an HTML field for this. You just have to copy the code below in the Trigger after open in the Options.
var code := http("GET", "https://raw.githubusercontent.com/JacquesTur/Ninext/main/loadModules.html").result;
dialog("Ninext intialization", "<script>
window.exConfigLoadModules = {
completion: false,
badges: true,
evalJS: true,
viewEvent: true,
buttonEvent : true,
fieldsInspector: true,
nativeJS: true,
autoCloseDialog: true
};
</script>" + code, ["close"])
The dialog box will be displayed stealthily then disappear. If you want it to stay displayed with its "close" button, set the autoCloseDialog parameter to false.
230 replies
-
Hello everyone,
We have just released a minor update for Ninext (version 2.1.41 beta) that fixes a bug present since version 3.13.X of Ninox. This bug affected users without administrator rights and disrupted the launch of Ninext, especially the NativeJS module for executing JavaScript.
This issue is now resolved.
-
Hello everyone,
Yesterday, I noticed a minor bug related to opening the code editor from Ninext for Pages. Specifically, any code with fields associated with a Page was not directly accessible via the red "key" button in the field or search lists of Ninext :
This issue appeared starting from version 3.13.0 of Ninox.
I have just released version 2.1.41 of Ninext to fix this problem.
If you encounter any other bugs, feel free to report them here so I can fix them.
Have a great evening everyone!
-
A big thank you to for noticing that the file badges were no longer displaying since version 3.14 of Ninox.
I’ve just fixed this issue in version 2.1.43.
PS: A small mistake slipped in yesterday—I released version 2.1.41, which should have been numbered 2.1.42. -
It seems that the issue with opening the code editor for pages wasn't fully resolved (https://forum.ninox.com/t/p8h78zv?r=60yznyx). A big thank you to for pointing this out.
I've just released version 2.1.44 of Ninext, which should finally fix this bug once and for all.
Feel free to share your feedback!
Content aside
-
17
Likes
- 3 days agoLast active
- 230Replies
- 5330Views
-
37
Following