This is fine if one is developing code that is "constrained" to a particular item type.
I develop code that is reusable in many different NinjaTrader item types. Essentially, it is library code that can be used in any AddOn, Indicator, Strategy, etc. It is code that has a non-NinjaTrader namespace, since it is not constrained to any particular NinjaTrader item type, but can be used in virtually any supported NinjaTrader code.
The use of sub-folders does not really work in this case. If one has created such "independent" code files in a top-level folder (e.g. AddOns) and one creates a sub-folder and moves the files to that sub-folder, the files are automatically edited by the Editor to change the namespace in the code to the relevant namespace of the parent folder (e.g. NinjaTrader.NinjaScript.AddOns). This, of course, is not what the developer intended. Also, having the files as part of any of the pre-defined folders implies that the code is specific to that particular type of NinjaTrader item, which it is not.
Please add a new feature to support these type of non-aligned code projects that underpin development of the recognised NinjaTrader item types. I would expect it to have at least these capabilities:
- Able to create a top-level parent folder, not part of any pre-defined folders, for non-aligned code
- Able to create sub-folders within the parent folder for similar code
- The parent folder and sub-folders do not enforce any namespace or item-specific forms on the code
- Supports all the normal capabilities of item-specific folders, including compilation, exclusion, etc
Comment