Ninext : Important information

Ninox developper
Jacques_TUR
updated 1 yr ago
28replies

This message is addressed to all those who use the Ninext project.
I regret to announce that the Ninext project will be unusable on Ninox very soon.

This should happen at the beginning of February.

While it is still possible to activate/deactivate Ninext voluntarily, it is very important that you evaluate now what this will change in your databases that use it.

For example, for those who put Ninext code in global functions, I invite you to save the code in a separate word processor, because it is possible that disabling Ninext creates errors and that Ninox won't let you access the functions anymore (it already happened to me for other errors).

For those who use NativeJS, you'll have to check where in your code you use JavaScript. To help you, I added a "Native JS" tab in the popup. It shows you where NativeJS is used.

Hurry up and update your code to make it Ninext independent before it is disabled and you lose the search tools in the code.

Also remember to keep a version 3.7 of the Mac application that you can always use to activate Ninext locally if you need it.

I still hope to be able to find a solution to reactivate Ninext one day, but I have no idea when that will be. Thank you all for supporting this project.

- Fred
- 1 yr ago
- Reported - view
what is going on? is this something that Ninox is doing?
- Alan_Cooke
- 1 yr ago
- Reported - view
How unfortunate....So many usesful features. There was a short script one could pop into a formula to badge attachments and comments a while ago. Not sure I still have that and it was Ninext independant as I recall. Does someone still have that somewhere

Going to miss the Filter alert BIG time!! :-(
- Mel_Charles
- 1 yr ago
- Reported - view
Jacques TUR What ever your reasons for closing down the Ninext project, I would like to say a huge thank you for giving us the opportunity to tap into your skill set and give us great insight into what Ninox could do if further developed by Ninox themselves.

I fervently hope that this is not the last we hear from you tho... as I was only just beginning to understand what you were doing

It has been a pleasure to read with much interest your posts sir !

kind regards

Mel
- Fred
- 1 yr ago
- Reported - view
I'm very sadden to hear that Ninext is disappearing. You have taken this community to the next level with your work and have inspired others to do the same, i.e. Dark Mode.

I hope this doesn't mean that we will be losing your appearances in this forum as well.

Again thank you for showing us what is possible and for extending all of our knowledge.
- Ninox developper
- Jacques_TUR
- 1 yr ago
- Reported - view
Thank you very much, I am touched by your comments .
- netSME_Sylvain_Moesching
- 1 yr ago
- Reported - view
Jacques TUR thank you for your smart approach in making Ninox even more flexible. I would love to see all this work , totally integrated in future versions of Ninox. Hope it will happen.
- Alan_Cooke
- 1 yr ago
- Reported - view
I assume this post is in connection with the new 3.8 version release. Is it advisable to remove the Global Functions script prior to this to avoid any mishaps or will it simply be there and not function?
- Ninox developper
  
  Jacques_TUR
  
  1 yr ago
  
  Reported - view
  Alan Cooke Yes, for the time being it is better to remove (or comment out) all code parts related to Ninext. Especially the global functions because I have already noticed that a code error in one procedure can cause the deletion of all global functions. It's always recoverable with an API/REST call, but it takes time.
- Alan_Cooke
  
  1 yr ago
  
  Reported - view
  Jacques TUR Thanks - going to miss the filter flag and badges for attached files BIG time :-(
- Alan_Cooke
  
  1 yr ago
  
  Reported - view
  Jacques TUR Is it at all possible to have the filter indicator without Ninext?
- Ninox developper
  
  Jacques_TUR
  
  1 yr ago
  
  Reported - view
  Alan Cooke Give me some time, I am looking at what will be possible in the future.
- UKenGB
- 1 yr ago
- Reported - view
Wow, that's a kicker. Only used Jacques stuff in one db and refrained from using it in others in fear of exactly this outcome.

Jacques, can you explain why this is occurring?
- Ninox developper
  
  Jacques_TUR
  
  1 yr ago
  
  Reported - view
  UKenGB Please, leave me a few days and I will come back to you with news and explanations, I promise you
- Ninox developper
- Jacques_TUR
- 1 yr ago
- Reported - view
Hello everyone,

I am writing this message to tell you that I still don't have any more information at the moment. This is a way to give you a sign of life.
I think that part of Ninext will be able to continue working in the future but I don't know which part and how long it will take me to adapt to the new version of Ninox.
Anyway, as soon as I hear anything, I'll let you know.

Have a nice day everyone.
- Alan_Cooke
  
  1 yr ago
  
  Reported - view
  Jacques TUR You will crack this one Jacques - have every faith in you.
- Ninox developper
  
  Jacques_TUR
  
  1 yr ago
  
  Reported - view
  Alan Cooke Thanks, but in fact it's more a case of not cracking the code, but working with what is provided by Ninox.
- Alan_Cooke
  
  1 yr ago
  
  Reported - view
  Jacques TUR "crack" is not meant in that way :-). It's term mening you will find a solution in a normal way. I have no doubt though that the term "crack" finds its roots in the more devious pursuit.
  
  "crack" n'est pas signifié de cette façon :-). C'est à terme que vous trouverez une solution de manière normale. Je n'ai aucun doute cependant que le terme "crack" trouve ses racines dans la poursuite la plus sournoise.
- Alan_Cooke
  
  1 yr ago
  
  Reported - view
  Alan Cooke I hope Google Translate is correct.
- Ninox developper
  
  Jacques_TUR
  
  1 yr ago
  
  Reported - view
  Alan Cooke Ha sorry, it was my poor English that misled me . The translation had done a good translation but I didn't believe it
- Ruben
- 1 yr ago
- Reported - view
Shame, I only just heard about this and the possibility to integrate multiple languages for field descriptions. Seems like some things would be quite useful
- Maurice
- 1 yr ago
- Reported - view
Hello Jaques,
I just updated the on premise version to 3.7.15. It seems that Ninext does not work completely with 3.7.15 (selection of columns in views). Can you approve this?

Maurice
- Ninox developper
  
  Jacques_TUR
  
  1 yr ago
  
  Reported - view
  Maurice Now, on the cloud with v3.7.15, it works fine on my end. But in a few days, it will not work anymore.
  
  In the future, to have the same possibility, you will have to create a custom list with html().
- Maurice
  
  1 yr ago
  
  Reported - view
  Jacques TUR That's interessting. Badges works and all the other things I put on true
  
  function getNinext() do var res := http("GET", "https://raw.githubusercontent.com/JacquesTur/Ninext/main/dist/ninext.js", {}, {}); var version := extractx(text(res.result), "(?:var exModulesVersion = ')(.*)(')", "", "$1"); res.result end; dialog("Ninext intialization", "<div style='white-space: normal;' ; id='exLoadModule'></div> <script> window.exConfigLoadModules = { badges: true, viewEvent: true, buttonEvent : true, fieldsInspector: true, nativeJS: true, tableView: true, debugTracer : false, languages : false, errorsViewer : false, darkMode : false, autoCloseDialog: true };" + getNinext() + "</script>", ["close"]);
  
  viewEevent does not work. Is something wrong/missing in the loading code? Before we used 3.7.7 and it worked.
- Ninox developper
  
  Jacques_TUR
  
  1 yr ago
  
  Reported - view
  Maurice If I use your initialization code, everything works fine on my cloud database, including ViewEvent.
  
  Could you share with me an apli with the problem or the code you put in your list?
- Maurice
  
  1 yr ago
  
  Reported - view
  Jacques TUR I just wanted to copy my code ... Now it works. Sorry for taking your time.

Content aside

3 Likes
1 yr agoLast active
28Replies
1397Views
21 Following

Ninext : Important information

28 replies

Content aside

Overview