Compiling Script from Command Line

[enlightened_j]

hi,

I usually edit the NT scripts using external editor. I am wondering if there's a way to compile scripts externally from command line. By doing that it can save me a lot of time opening my script from NT editor and compiling it from the editor.

If that's not soemthing doable, please add a feature that will check the timestamp of the opened file in the NT editor and reload the file if the timestamp of the file is newer than the last time NT editor write the file to disk. If the editor has this featuer, there will be no need for me to re-open the file every single time I make a change exteranlly and need to re-compile the script. Thank.

J

[NinjaTrader_Ben]

Hello,

Compiling externally is not supported.

I will forward your suggestion to our development department for consideration.

[hemlock]

J,

When you compile ANY script from within Ninja ALL scripts are compiled.

I too use an external editor to edit Ninja scripts (Visual Studio in my case). What I do is just open any script file within the Ninja editor and leave it open. When I have completed my editing is VS and saved my changes I just switch to the open editor in Ninja and compile. No need to open within Ninja the specific script you were editing in your external editor. The script that you keep open in the Ninja editor can be any script, it does not matter which one, but preferably not any that you are editing externally. Hope that makes sense.

Although I do wish that the "Indicator successfully generated" would not pop up everytime you compile.

[NinjaTrader_Bertrand]

Thanks for the input hemlock!

[Brian1]

Hey Hemlock ... great idea that's gonna save me lots of time.

Much appreciated.

Brian1

[NinjaTrader_Dierk]

>> I too use an external editor to edit Ninja scripts (Visual Studio in my case)
Be forewarned: this is not recommended, since the NT editor amends the code and adds logic as needed for proper operation.

We are unable to support issues resulting from editing the code outside the NT editor.

[hemlock]

The editor itself amends (adds/changes) code?

Can you give an example?

[NinjaTrader_Dierk]

Unfortunately this is beyond the scope of what we can provide support for.

[hemlock]

Dierk,

Are you referring to the code at the bottom of an indicator marked "NinjaScript generated code. Neither change nor remove." that gets generated when the code is created from the wizard? Does this get changed after the initial creation?

[NinjaTrader_JoshP]

hemlock,

The section in there should never be touched and we do not support any modifications in there.

[hemlock]

Thanks Josh I understand that, but that was not the question that I asked.

[NinjaTrader_JoshP]

hemlock,

We do not support anything about that section. Unfortunately there is no further information I can provide.

[roonius]

Dierk,

Are you referring to the code at the bottom of an indicator marked "NinjaScript generated code. Neither change nor remove." that gets generated when the code is created from the wizard? Does this get changed after the initial creation?

Yes, it does change after wizard creates the code. It might change after each compilation - depends on what you have changed in your code.

[hemlock]

Thanks roonius.

To anyone following my suggestion in post #3 in regards to editing Ninja script in an external editor, please be advised of the following:

1. It appears that if you add additional parameters/properties to an indicator via the procedure posted here http://www.ninjatrader-support2.com/...ead.php?t=5782 then the Ninja editor modifies the code at the bottom of an indicator at compilation time to reflect the additions. I suggest that if you use an external editor to add new parameters/properties to an indicator that the script be opened and compiled with the Ninja editor to faciliate this code modification.

2. This probably is true for modifiying or deleting parameters/properties as well.

3. Following any of my advice is done so at your own risk.

Ken

[r2kTrader]

Hemlock,

Do a search on this forum for AutoHotKey. I used that for the purpose of automating NT to do things it doesn't have the capability to do. For example restart automatically and reconnect to a connection and launch a strategy.

My guess is that you could do as are you are doing, and then have AutoHotKey actually run the compile command and then hit the ok button for you. So with a simple keystroke, you can compile and click the ok without having to hunt for the ok button or make certain windows active. Part of this would also have you return to your original script. You could put this as a shortcut in your quicklaunch bar and then every time you want to compile, just click that shortcut, let the windows blink and do their thing, and then you will be returned to your VS window.

It's a thought, hope it helps.

J,

When you compile ANY script from within Ninja ALL scripts are compiled.

I too use an external editor to edit Ninja scripts (Visual Studio in my case). What I do is just open any script file within the Ninja editor and leave it open. When I have completed my editing is VS and saved my changes I just switch to the open editor in Ninja and compile. No need to open within Ninja the specific script you were editing in your external editor. The script that you keep open in the Ninja editor can be any script, it does not matter which one, but preferably not any that you are editing externally. Hope that makes sense.

Although I do wish that the "Indicator successfully generated" would not pop up everytime you compile.