Use of NeoScriptToJS
Quote from Gaev on September 19, 2020, 7:03 pmIf I have multiple Javascript subroutines that need to call another Javascript subroutine, do I need to precede each/any of the calls with NeoScriptToJS ? ... like this ...
NeoScriptToJS neosubroutine.myCommonJavascriptSubroutinee(a,b,c); if ($App[pqrs] == "xyz") { blah blah blah }... or even ...
NeoScriptToJS returnValue = neosubroutine.myCommonJavascriptSubroutinee(a,b,c); if (returnValue == "xyz") { blah blah blah }Is it any different if all such subroutines are actually part of a plugin ?
If I have multiple Javascript subroutines that need to call another Javascript subroutine, do I need to precede each/any of the calls with NeoScriptToJS ? ... like this ...
NeoScriptToJS
neosubroutine.myCommonJavascriptSubroutinee(a,b,c);
if ($App[pqrs] == "xyz") {
blah blah blah
}
... or even ...
NeoScriptToJS
returnValue = neosubroutine.myCommonJavascriptSubroutinee(a,b,c);
if (returnValue == "xyz") {
blah blah blah
}
Is it any different if all such subroutines are actually part of a plugin ?
Quote from luishp on September 20, 2020, 11:32 am@gaev if they are all JavaScript functions within the same plugin, and you want to use them from the plugin too, then you can call them directly. No need to use NeoScriptToJS.
Regards.
@gaev if they are all JavaScript functions within the same plugin, and you want to use them from the plugin too, then you can call them directly. No need to use NeoScriptToJS.
Regards.
Quote from luishp on September 20, 2020, 11:37 am@gaev, when developing plugins I usually open the plugin source file within Notepad++ in order to clone similar commands copy-pasting the corresponding XML code. Then I reload it into the Plugin Generator.
As testing a plugin under development is really quick (compile and install takes a fraction of a second) I would recommend you developing the plugin directly as a plugin and not as subroutines to be ported later to a plugin.Best regards.
@gaev, when developing plugins I usually open the plugin source file within Notepad++ in order to clone similar commands copy-pasting the corresponding XML code. Then I reload it into the Plugin Generator.
As testing a plugin under development is really quick (compile and install takes a fraction of a second) I would recommend you developing the plugin directly as a plugin and not as subroutines to be ported later to a plugin.
Best regards.