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.

175 replies

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

    I am really sorry 😔.

    Several of you are having issues with the copy/paste function not working in certain configurations, or not working at all. I had tested it on Chrome, Safari, and Firefox on Mac, and on Chrome and Firefox on PC, and everything was working fine 🤔.
    Following your messages, I looked into what could be causing the issue and found some flaws that might work for certain browser configurations but not for others. I hope this is the root of the problem because, unfortunately, I have not been able to reproduce the issue so far.

    I have just released version 2.1.27 beta and hope that this will fix your problems.

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

      Good catch  that's exactly the problem 👍.

    • Fred
    • 6 mths ago
    • Reported - view

    Hi -

    What is the code without looking for a local table, that we put in the Trigger after open? I'm trying to create a test DB you can access.

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

        

      var res := http("GET", "https://www.ninext.fr/_functions/ninext").result.code;
      dialog("Ninext initialization", html("<script ninext=''>
      " +
      res +
      "
      ninext.start({
          badges: true,
          viewEvent: true,
          buttonEvent : true,
          fieldsInspector: true,
             nativeJS: true,
          tableView: true,
          debugTracer : true,
          languages : false,
          errorsViewer : true,
           codeFinder : true,
          autoCloseDialog:  false })
      </script>"), ["close"])
      
    • Ninox developper
    • Jacques_TUR
    • 6 mths ago
    • Reported - view

    Many thanks to for sharing his application with me 🙏.
    I was able to reproduce the issue. It was the case where a form was displayed directly, without going through a table.
    I have just released version 2.1.28 beta, which fixes this.

      • Fred
      • 6 mths ago
      • Reported - view

      We all wish other software developers were as responsive. Thanks, Jacques, for making Ninext an indispensable toolkit.

    • Icarus_Ralf_Becker
    • 5 mths ago
    • Reported - view

    Good morning Jacques, I would like to ask you if it is possible to make the copy&paste feature for elements also available in the table settings section:

    Now copy&paste is just possible for visible elements, but often a lot of fields are hidden. Hidden objects could be copied & pasted from this view very fast and you don't need to change the visibility scripts to duplicate them. Thank you in advanced for checking this.

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

       It's a very good idea. I'll see how I could do that.

    • Icarus_Ralf_Becker
    • 4 mths ago
    • Reported - view

    Hey , i recently found a Bug. If Ninext is running, all the tabs in pages are not visible. Can you check that please? Best,

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

       thank you 🙏 .
      Indeed I discovered that this week. I have just fixed the issue and uploaded version 2.1.29.
      This version also fixes a problem when using the callNinoxFunction to run a global Ninox function.

      • Icarus_Ralf_Becker
      • 4 mths ago
      • Reported - view

       Good morning, I see it, but all the tabs are right align and not left align, so you just see 2 tabs and the rest is out of the viewport. 

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

    Sorry Icarus - Ralf Becker , I got the wrong bug 😅. Actually, there were several.
    I just released version 2.1.30 which, along with version 2.1.29, fixes the following bugs:

    • The use of callNinoxFunction does not work with Ninox's global functions,
    • The red key button for quick access to the code in the Ninext popup does not work with pages,
    • The tabs of the pages do not display,
    • When starting an application, if the form (or page) is displayed before Ninext has finished loading, the onUpdate event in the tabs is not called. You have to close and reopen the form for it to start working normally.

    Pages in Ninox are not managed the same way as forms. Therefore, I have to adapt my code for two different operations, and this has let some bugs slip through. If you find any others, please don't hesitate to let me know. Until then, have fun.

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

       Since version 3.10.8 of Ninox, calls to JavaScript with Native JS ( #{...}# ) no longer work. I have released a version 2.1.31 to fix this.

    • Icarus_Ralf_Becker
    • 2 mths ago
    • Reported - view

    Hi ,

    I hope, you are fine. It was just a little bit "quiet" in this forum 😉

    I have a suggestion for improvement:

    If you search for a certain variable used in the scripts, it is yellow marked the scripts as an eyecatcher. Which is really great, especially if the script is long.

    But after the first action using the keyboard, the marks disappear.

    It would be great, if the yellow marks would be available until the editors is closed. 

    Thank you very much und best regards,

     

    Ralf

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

       Yes, it's a very good idea. I wanted to do that from the beginning, but unfortunately, I couldn't because after modifying the text, Ninox refreshes the text editor, and I no longer have control to highlight the texts.

    • Patrick_W
    • 2 mths ago
    • Reported - view

     with 3.11 there are many errors with Ninext. I didn't test the modules individually. But when I disabled the loading of Ninext, the performance is back and fine. With Ninext the console throws many lines about errors.

      • Fred
      • 2 mths ago
      • Reported - view

      I don't see any major issue on my end. The one thing that is noticable that the script run time at login is slower. Averages 0.4 secs (according to Ninext. Around 7 seconds in real time.) when it use to be in around 0.1 secs.

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

       It appears that it is a user interaction tracking cookie that is being disrupted by Ninext (https://www.rrweb.io). If I block cookies on my page, there is no longer an error.

      I am troubled because it seems well protected, and I cannot trace its code to see where the error is coming from. I will have to do it step by step, and it might take a lot of time. Are you completely blocked by this issue at the moment?

      • Patrick_W
      • 2 mths ago
      • Reported - view

       I used it commonly in a customers database for easier js. But I turn it of until it is fixed. I tried to find that cookie to block but I couldn't. And the customer has also to block the cookies.

      Do you have a quick solution to check the screen size of the user? With nativeJS I used it like:

      #{return window.screen.width }# < 800
      
      • Ninox developper
      • Jacques_TUR
      • 2 mths ago
      • Reported - view

       Without running JavaScript I can't see a solution. 
      On the other hand, the module that seems to be causing problems with rrweb is FieldsInspector. If you deactivate it everything should work fine and you can continue to use NativeJS with your code. 

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

       Sorry for all this, it's not a real solution, it's just waiting for me to fix this bug.

    • Ninox developper
    • Jacques_TUR
    • 2 mths ago
    • Reported - view
     said:
    I hope, you are fine. It was just a little bit "quiet" in this forum 

     Yes, I also think it's been a long time since I've evolved Ninox. I'm preparing a surprise for you, but it takes a bit of time to come out.

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

    Hello everyone, 

    I've fixed the bug with https://www.rrweb.io cookie. You should now be able to use it again at normal speed. In any case, the errors in the development console have disappeared.

    Version 2.1.32 beta is now online.

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

    Hello,
    I just published version 2.1.33 beta of Ninext to fix a bug in an unusual case:

    When the same variable is declared twice with the debug function after each declaration, the entire code is not executed.

    Example:

    var a := 1;
    debug("A1");
    var a := 2;
    debug("A2");
    alert(a);
    • Robert_Deimel
    • 12 days ago
    • Reported - view

    I tried to use Ninext but, I don't get anything working and the Github links are dead. Is the project still available?

      • Ninox developper
      • Jacques_TUR
      • 12 days ago
      • Reported - view

       yes, the project is still available. However, the sources are no longer available and that's why the GutHub link doesn't work.

      If you want to install Ninext on your database, send me an email at jacques.tur@umangenius.com and I'll send you the installation procedure.

Content aside

  • 15 Likes
  • 12 days agoLast active
  • 175Replies
  • 4192Views
  • 34 Following