Coding Standards - DRAFT 2009 09 30 - NinjaTrader Programming | futures io social day trading
futures io futures trading


Coding Standards - DRAFT 2009 09 30
Updated: Views / Replies:1,489 / 0
Created: by Saroj Attachments:0

Welcome to futures io.

(If you already have an account, login at the top of the page)

futures io is the largest futures trading community on the planet, with over 90,000 members. At futures io, our goal has always been and always will be to create a friendly, positive, forward-thinking community where members can openly share and discuss everything the world of trading has to offer. The community is one of the friendliest you will find on any subject, with members going out of their way to help others. Some of the primary differences between futures io and other trading sites revolve around the standards of our community. Those standards include a code of conduct for our members, as well as extremely high standards that govern which partners we do business with, and which products or services we recommend to our members.

At futures io, our focus is on quality education. No hype, gimmicks, or secret sauce. The truth is: trading is hard. To succeed, you need to surround yourself with the right support system, educational content, and trading mentors Ė all of which you can find on futures io, utilizing our social trading environment.

With futures io, you can find honest trading reviews on brokers, trading rooms, indicator packages, trading strategies, and much more. Our trading review process is highly moderated to ensure that only genuine users are allowed, so you donít need to worry about fake reviews.

We are fundamentally different than most other trading sites:
  • We are here to help. Just let us know what you need.
  • We work extremely hard to keep things positive in our community.
  • We do not tolerate rude behavior, trolling, or vendors advertising in posts.
  • We firmly believe in and encourage sharing. The holy grail is within you, we can help you find it.
  • We expect our members to participate and become a part of the community. Help yourself by helping others.

You'll need to register in order to view the content of the threads and start contributing to our community.  It's free and simple.

-- Big Mike, Site Administrator

Reply
 
Thread Tools Search this Thread
 

Coding Standards - DRAFT 2009 09 30

  #1 (permalink)
Elite Member
Arcata, CA
 
Futures Experience: Intermediate
Platform: NinjaTrader
Favorite Futures: index futures, oil
 
Saroj's Avatar
 
Posts: 482 since Jun 2009
Thanks: 223 given, 389 received

Coding Standards - DRAFT 2009 09 30

Here is my first cut at suggested coding standards for futures.io (formerly BMT). I welcome comments and suggestions... following these simple guidelines will save us all a frustrating experience such as RJay posted today.


1. If you are modifying someone else’s indicator (or strategy), first rename it, by:
- right click and select “Save As”; enter a descriptive name and assign a version number. Include a mneumonic that identifies you "RJay" preferably before the version number.
- whether starting from an existing code file or from scratch, use appropriate names and version numbers:
- Version numbers:
- NT doesn’t like periods in the name so use underscores; like this: “_v1_0” at the end of the name. The first number, “1” in this case, designates a major version; the 2nd number, “0” in this case, designates minor changes (tweaks).
- Change the names: i. at minimum change “public class nnn_RJay_v1_0 : Indicator” - also good idea to change the name in “[Gui.Design.DisplayName(“nnn_RJay_v1_0”)]; this will avoid confusion in knowing which indicator version is on a chart as this is the name that is displayed in the Indicator list for a chart.
2. Description and logging changes
- In the summary area, enter a description of the code
- Indicate which external files it references “SMA(Close, Period)” for instance, so the user knows what else is required to successfully use the indicator.
- Mention what the source code was, “based on ADXVMA” for instance.
- Log changes as you make version releases: for example: “2009 09 16 – Saroj - added capability of sound alerts”
- Include the name since others might make changes if a collaborative effort; this way, if there is a subsequent problem that person can be consulted.
3. Include liberal comments to create a pseudo code type understanding of the logic (not really necessary for very simple code files, but very helpful none-the-less; especially if someone else might be making changes later.
4. Organize routines by using “#region … #endregion” tags to make the code easier to read (Optional but helpful for complex code)5. Be sure you get a clean compile before closing the file. If you can’t resolve an error, comment it out with an explanation. NT will not allow any other compiles if even ONE indicator has an error in it.


Last edited by Saroj; September 30th, 2009 at 02:18 PM.
Reply With Quote
The following 5 users say Thank You to Saroj for this post:

Reply



futures io > > > > > Coding Standards - DRAFT 2009 09 30

Thread Tools Search this Thread
Search this Thread:

Advanced Search



Upcoming Webinars and Events (4:30PM ET unless noted)

Jigsaw Trading: TBA

Elite only

FuturesTrader71: TBA

Elite only

NinjaTrader: TBA

Jan 18

RandBots: TBA

Jan 23

GFF Brokers & CME Group: Futures & Bitcoin

Elite only

Adam Grimes: TBA

Elite only

Ran Aroussi: TBA

Elite only
     

Similar Threads
Thread Thread Starter Forum Replies Last Post
Webinar: Basic NinjaScript coding, May 25th @ 4:30PM Eastern, 22:30 Berlin/Paris sam028 The Elite Circle 33 August 11th, 2011 11:37 AM
EU Willing to Let Greece Default Under New Plan: Draft Quick Summary News and Current Events 0 July 21st, 2011 10:20 AM
EU Racing to Draft Second Greek Bailout Quick Summary News and Current Events 0 May 30th, 2011 08:50 PM
Banks Ease Lending Standards for First Time in Four Years Quick Summary News and Current Events 0 August 16th, 2010 04:20 PM
Coding Standards Saroj NinjaTrader Programming 0 July 10th, 2009 12:31 AM


All times are GMT -4. The time now is 03:40 PM.

Copyright © 2017 by futures io, s.a., Av Ricardo J. Alfaro, Century Tower, Panama, +507 833-9432, info@futures.io
All information is for educational use only and is not investment advice.
There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
no new posts
Page generated 2017-12-17 in 0.07 seconds with 19 queries on phoenix via your IP 107.20.115.174