Please consider these changes to the NinjaScript Compiler:
1) When a NinjaScript is successfully compiled the compiler displays the informational message:
Indicator successfully generated
OK
Suggestion: There is only one button to click. Instead of forcing the programmer to acknowledge the message by clicking the OK button, wait a few seconds then beep and close the window for then.
2) If Debug Mode is selected, before EVERY NinjaScript compile begins, the compiler presents the message:
Enabling "Debug Mode" should only be used by advanced programmers that intend to debug their NinjaScript code in Visual Studio. Compiling
NinjaScript objects with this mode enabled will results in a run time performance penalty.
PLEASE MAKE SURE YOU DISABLE THIS MODE ONCE YOU ARE COMPLETE WITH YOUR DEBUG AND RECOMPILE YOUR NINJASCRIPT OBJECTS.
OK
The compiler waits for the message to be acknowledged, by clicking OK, before it begins.
Suggestion: Combine the "Indicator successfully generated". and 'Enabling "Debug Mode" messages into one message that is presented after a successful compile. Something like:
Indicator successfully generated
Enabling "Debug Mode" should only be used by advanced programmers that intend to debug their NinjaScript code in Visual Studio. Compiling
NinjaScript objects with this mode enabled will results in a run time performance penalty.
PLEASE MAKE SURE YOU DISABLE THIS MODE ONCE YOU ARE COMPLETE WITH YOUR DEBUG AND RECOMPILE YOUR NINJASCRIPT OBJECTS.
OK
If this suggestion is not acceptable for some reason, then how about presenting the message only for the first compile of the day.
While seemingly small annoyances they add up quickly by causing unnecessary hand/mouse movements, wasted time, and breaks in concentration.
1) When a NinjaScript is successfully compiled the compiler displays the informational message:
Indicator successfully generated
OK
Suggestion: There is only one button to click. Instead of forcing the programmer to acknowledge the message by clicking the OK button, wait a few seconds then beep and close the window for then.
2) If Debug Mode is selected, before EVERY NinjaScript compile begins, the compiler presents the message:
Enabling "Debug Mode" should only be used by advanced programmers that intend to debug their NinjaScript code in Visual Studio. Compiling
NinjaScript objects with this mode enabled will results in a run time performance penalty.
PLEASE MAKE SURE YOU DISABLE THIS MODE ONCE YOU ARE COMPLETE WITH YOUR DEBUG AND RECOMPILE YOUR NINJASCRIPT OBJECTS.
OK
The compiler waits for the message to be acknowledged, by clicking OK, before it begins.
Suggestion: Combine the "Indicator successfully generated". and 'Enabling "Debug Mode" messages into one message that is presented after a successful compile. Something like:
Indicator successfully generated
Enabling "Debug Mode" should only be used by advanced programmers that intend to debug their NinjaScript code in Visual Studio. Compiling
NinjaScript objects with this mode enabled will results in a run time performance penalty.
PLEASE MAKE SURE YOU DISABLE THIS MODE ONCE YOU ARE COMPLETE WITH YOUR DEBUG AND RECOMPILE YOUR NINJASCRIPT OBJECTS.
OK
If this suggestion is not acceptable for some reason, then how about presenting the message only for the first compile of the day.
While seemingly small annoyances they add up quickly by causing unnecessary hand/mouse movements, wasted time, and breaks in concentration.
Comment