Why programmers requests are ignored in New releases?

[TazoTodua]

Hi NT support,
I've seen that new NT8 update released (yesterday , see release notes)

However, I feel very dissapointed, as (like in previous updates), many our (programmers) minor (and simple) requests were ignored. I say, almost none of the NinjaScript related problems/features were fixed/added. (importants bolded)


For example I had a bunch of useful and simple requests:


- ability to compile script after copying manually from outside (https://ninjatrader.com/support/foru...d.php?t=108906 and https://ninjatrader.com/support/foru...d.php?t=108640)

- property to completely hide indicator from list ( https://ninjatrader.com/support/foru...d.php?t=107715 )

- change parameter without reloading all indis ( https://ninjatrader.com/support/foru...d.php?t=108843 and https://ninjatrader.com/support/foru...d.php?t=107562 )

- make properties also available as inputs across derived class ( https://ninjatrader.com/support/foru...d.php?t=108828 and https://ninjatrader.com/support/foru...d.php?t=108548)

- include system indicators (into exported package) with just referencing, without adding them into package (avoiding overwrite problems) ( https://ninjatrader.com/support/foru...d.php?t=108797)

- IDE changes ( https://ninjatrader.com/support/foru...151#post537151 )

- exact & detailed information for Exceptions/StackTraces ( https://ninjatrader.com/support/foru...d.php?t=108564 and https://ninjatrader.com/support/foru...d.php?t=104239 )

- Add unique Identifier to chart (or only when chart is open), so any indi could access i.e. ChartContol.ID and they could detect (while they communicate with each other) if they are on same chart. (rarely needed this too)

- no need to restart NT after import ( https://ninjatrader.com/support/foru...d.php?t=103903)

- add indicators from indicators, not only from strategy; ( https://ninjatrader.com/support/foru...d.php?t=108368)

- adding flexible ZOrder property to all objects and plots ( https://ninjatrader.com/support/foru...d.php?t=108359 )

- forum suggestions ( https://ninjatrader.com/support/foru...d.php?t=103996 and this )

- like indicator, after strategy fires error, it should have an option i.e. development property/field, set to true) which will enable it again after clicking F5 (reload) (https://ninjatrader.com/support/foru...d.php?t=101399)

- populate chart with simulated bars on load , when Simulated DataFeed is connected ( https://ninjatrader.com/support/foru...d.php?t=103242 )

- adding Size to DrawObjects ( https://ninjatrader.com/support/foru...d.php?t=108113 and https://ninjatrader.com/support/foru...d.php?t=107510)

- a more Position slots on charts ( https://ninjatrader.com/support/foru...d.php?t=108123 )

- ability to set databox rounding from indicator ( https://ninjatrader.com/support/foru...d.php?t=108040 )

- commands in NT ( https://ninjatrader.com/support/foru...823#post516823 ) + button in forum topics, to mark our topic here as "resolved"

- using "using" parameter wont correctly referenced in exported package, missing full reference (https://ninjatrader.com/support/foru...d.php?p=533327)
+ obvious lack of Exporter to correctly write full references ( https://ninjatrader.com/support/foru...886#post532886 + https://ninjatrader.com/support/foru...d.php?t=106066 )

- bunch of suggestions ( https://ninjatrader.com/support/foru...d.php?t=107360 )

- as an exception, i think (with NinjaScript wizard) to include underscore in Indicator/Strategy names ( https://ninjatrader.com/support/foru...d.php?t=106796 )

- make NT to handle Unserializable properties too (without giving error "couldnt reflect type") while trying to save template for indicator, that includes different kind of public propertiy types ( https://ninjatrader.com/support/foru...d.php?t=107691 and https://ninjatrader.com/support/foru...d.php?t=107234 and https://ninjatrader.com/support/foru...d.php?t=104642)

- having organised/nice list during export ( https://ninjatrader.com/support/foru...d.php?t=107567 )

- Show definitions in IDE ( https://ninjatrader.com/support/foru...d.php?t=104619 )

- better documentation for properties ( https://ninjatrader.com/support/foru...d.php?t=107555 )

- show/hide some inputs according to our custom field ( https://ninjatrader.com/support/foru...376#post532376 )

- ability to set default value with the property declaration ( https://ninjatrader.com/support/foru...d.php?t=107558 )

- default folder-location when file-dialog opens ( https://ninjatrader.com/support/foru...d.php?t=107400 )

- simplest request for searchbox, that could saved our minutes everyday ( https://ninjatrader.com/support/foru...d.php?t=103641 )

- another modification of searchbox ( https://ninjatrader.com/support/foru...d.php?t=103162 )

- add overload to PlaySound which determines to fire Alarm once in a bar or on every tick ( https://ninjatrader.com/support/foru...d.php?t=107392 ) [p.s. in ThinkOrSwim there exists Alert.Once or Alert.Bar parameters]

- search results correction in google ( https://ninjatrader.com/support/foru...d.php?t=107235 )

- upon installing the NT, create a protocol in Windows, to open the platorm with URL ( https://ninjatrader.com/support/foru...d.php?t=103178 )

- add a property to hide a plot from chart ( https://ninjatrader.com/support/foru...d.php?t=103168 )

- add a new property in run-time NT global namespaces, like : InstanceType property, which will determine whether script is attached to chart or marketanalyzer ( https://ninjatrader.com/support/foru...d.php?t=103160 )

I hope you know well more then me, that making the platform programatically advanced and attractive for programmers, make it much wide-spread and preferred platform for programmers. So, dont ignore programmers' requests please.

thanks

[NinjaTrader_JoshG]

Hello TazoTodua,
Thanks for your post.

Our development team is tracking these requests based on demand and feasibility. There is no guarantee if or when a request will become a feature.

Please continue to monitor the release notes for updates and let us know if you have any further questions.

NinjaTrader 8 Release Notes

[eDanny]

My 2 cents is that I think demand is a bad way to determine if a change is useful. If I think up a change that could benefit everyone but no one else thought about it, would it be impractical because there is no demand? People read these change requests and many times think the idea is great, and then continue to the next post. Does that mean there is no demand?

[NinjaTrader_JoshG]

Hello eDanny,

I would suggest for anyone that agrees with a feature request to submit their vote for that feature as well before moving to the next post. Otherwise, it will likely be viewed as a feature request with little demand.

[aerofly]

Josh,
I agree with You but at moment there isn't a voting feature on forum to vote and track polling.
If I'm not in error when there is a request posted from someone we can only post "please add my vote".
I think this is a bit discouraging for many people.
Just my 2 cents.

[TazoTodua]

Absolutely agree. The demand should be measured by the forum (as only 5 % of NT platform users might be posting here). Instead, you NT devs should think, if particular request is worth to do or not for the sake of completness.
Did anyone (or i guess, max 1-2 persons) requested that NT editor should have Find & Replace window? probably no-one requested, but you definitely know that it's usefull for us.

so, there exists a generic term - if there is one user who needs that, probably there are many other users behind it, who will use that too.

NT support, please you frankly, while looking those listed requests (and especially bolded one), dont you agree that those are useful not only for me, but many programmers?

please, just tell frankly.

[NinjaTrader_JoshG]

Hello aerofly,
Thanks for your post.

A voting feature on the forum would be great! For now though, I suggest users take the extra 2 seconds to submit a comment as a vote so that their thoughts and suggestions are considered.

TazoTodua, demand is measured in part by user interest. When other members comment in favor of a suggestion then it may be more likely to be explored by our development team. I agree that there are features that would be nice to have, and many of the ones you noted could be found useful by more than just yourself.

[NinjaTrader_Ray]

Deciding on features for future releases is not a simple black and white decision. There are many factors involved including but not limited to:

• Demand which is measured by objective user requests and subjective discretion on the part of our product management team and myself
• Feasibility
• Developer bandwidth
• Current projects in the queue
• Economics

Customer feedback is important and we appreciate you taking your time to provide us insight on how we can improve our product.