15

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.

188 replies

null
    • Ninox developper
    • Jacques_TUR
    • 2 mths ago
    • Reported - view

    Following the remark from , I quickly fixed the bug that prevented the proper functioning of the OnClick event in the view fields. I also found other potential errors in the OnUpdate event for buttons. I favored a quick update to avoid leaving users in trouble. This means that there may still be bugs. If that's the case, please let me know.

    Version 2.1.35 beta is now online.

    I would like to remind you that Ninext remains an experimental project and that Ninox can modify the core of its code in such a way that it no longer functions. We can hope that the maintenance tools continue to work. Regarding interface modifications such as badges, OnClick and OnUpdate events, as well as the execution of JavaScript via NativeJS, there is a good chance that they may not function in the near future. Therefore, I encourage you to use them only on non-commercial projects, or have a plan B in case of failure.
    Ninox takes care to submit their beta versions of updates to me before they are released. Thus, I will be notified in advance if this happens. Although we can see today that, regarding the OnClick event, I did not anticipate the bug 😅.

    • Alan_Cooke
    • 2 mths ago
    • Reported - view

    Is there a sample database that uses the onClick event.  Better yet one that uses all the Ninext features?

      • Ninox developper
      • Jacques_TUR
      • 2 mths ago
      • Reported - view

       Yes, here's an example application. The OnClick example is in ViewEvent => List of customers => formula
       

    • Ninox developper
    • Jacques_TUR
    • 1 mth ago
    • Reported - view

    I've just updated Ninext to version 2.1.36 beta to add a basic database analysis function.
    see here: https://forum.ninox.com/t/g9ym625?r=83ymmd9

    • Maurice
    • 1 mth ago
    • Reported - view

    Hello Jacques,

    I get many error warnings

    but I can not find any error.

    "Dienststellen Link" is a n:1 relationship do a another database in the team. All the errors are concerning die related database.

    Regards Maurice

      • Ninox developper
      • Jacques_TUR
      • 1 mth ago
      • Reported - view

      This sometimes happens when a field is deleted. The column no longer appears, but the error exists in the Ninox schema without the user being able to see it or be affected by it. To remove the error, click on the red button to access the code, then confirm the window that appears on the screen by clicking the OK button. The error should disappear.

       

      • Maurice
      • 1 mth ago
      • Reported - view

       I get no OK-Button. It looks like this:

      Maybe it is because of that "Dienststellen Link" is a relation to another database in the same team. It is not a relation to a table inside the same database.

      • Ninox developper
      • Jacques_TUR
      • 1 mth ago
      • Reported - view

       And in this other table, does Ninext detect an error?

      • Maurice
      • 1 mth ago
      • Reported - view

       I found some (9 errors), but "zeroed" them. Now there are no errors in the original database. In the one I have the 46 errors, they are still there.

      • Ninox developper
      • Jacques_TUR
      • 1 mth ago
      • Reported - view

       I couldn't reproduce the problem. Could you send me a copy of these tables so I can see what's going on?

      • Maurice
      • 2 wk ago
      • Reported - view

       Hi Jacques, I still have this ToDo on my list. But in the last few weeks I was so busy. Sorry. I even do not know if I get it before my holidays. Juts want you to know: still on my list. Ninox works with your plugin.

    • Icarus_Ralf_Becker
    • 1 mth ago
    • Reported - view

    Good morning  , last year I recommended an import and export function for the strings in the localization feature.

    I asked you to think about it, because I have a database with more than 1000 strings and I would like to use translator software to translate them into different languages. To do this manually cell by cell is not useful. 

    So, do you think this feature is possible to add?

    Best,

      • Ninox developper
      • Jacques_TUR
      • 1 mth ago
      • Reported - view

      Dear   I suppose you are referring to this post: https://forum.ninox.com/t/p8h78zv?r=83ha73q.

      To answer your question, I haven’t taken any concrete action yet because I haven’t obtained Ninox’s agreement to develop a sustainable add-on, especially regarding multilingual support. Using this feature for a professional application could be risky, as Ninox could remove this possibility at any time.

      A less risky solution would be to dynamically replace the titles of each field with a JavaScript loop that runs regularly to update the display. This method would directly modify the titles in the HTML, providing a temporary but more independent solution from Ninox.

      It would also be helpful if users continue to inform Ninox about the importance of having a multilingual interface. The more of us express this need, the better our chances of getting a favorable response.

Content aside

  • 15 Likes
  • 2 wk agoLast active
  • 188Replies
  • 4634Views
  • 33 Following