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.
243 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! -
Many thanks to Bruce Kieffer for pointing out the issue with badges on the paperclip that were no longer working in version 3.13.6 of the Mac app.
I’ve fixed this issue, along with a parameter call error in the ninext.callNinoxFunction function.
Version 2.1.45 Beta is now live.
Wishing everyone a wonderful holiday season!
-
How do I down load and use the latest version? Is there a fee?
-
Hello everyone,
I have just released version 2.1.47 beta of Ninext, which fixes:
- a rare bug causing tabs to be displayed when the "Displays field only, if" trigger returns false. In this case, the tab remains visible until the user clicks on it;
- the removal of the search field in the field editing window to keep the one provided by Ninox since version 2.14;
- an update to the window resizing function to ensure compatibility with version 3.15, which will be released tomorrow.
Enjoy
! -
Found an issue with 3.15.
When I open a record in a table it opens like:
I tried another DB and had no issues. Then I took out the Ninext opening script and reopened the DB and all was fine.
What is the code to run Ninext without saving data to local table?
This happens in Edge (Win) and Firefox (Win/Mac).
Ok, with Safari and Zen 1.7.2b (Win).
-
Now it is happening in Chrome (Win).
-
You're right. In the very specific case where you close your database after partially opening a form, then reduce the browser window and reopen the database with Ninext, the display bug you mentioned does indeed occur. I'll look into it.
As for the form overlapping the table list, this is a bug that exists in Ninox, even without Ninext. It has been present since version 3.14. I discovered it this week and carried out checks before the release of version 3.15 of Ninox. It does not come from Ninext.
I can reproduce it with a standard database. Simply open a first form, then a sub-form that overlaps it slightly. Then, by reducing the browser window, the form underneath appears over the table list.
-
Thank you
Version 2.1.48 beta is now online and fixes this bug. -
Thanks, but that wasn't what was happening in my picture. I need to get an animated gif maker. :) I was just opening a record and the record view popped out to the left in the table area. The window was big enough to open the view.
Your fix worked and now the view opens properly.
-
-
said:
What is the code to run Ninext without saving data to local table?I'm not sure I understand which code and data you're referring to. Could you clarify?
Content aside
-
17
Likes
- yesterdayLast active
- 243Replies
- 5670Views
-
38
Following