Ashish, I think now is the time to conduct a final refactoring of the control.
I think this should be the strategy:
1). the sonar-d.html will contain all of the test data & functionality, plus the html skeleton
2). the d3.sonar.js file will contain the code that will get used in my project
So, all the code to do with random numbers will be in 1). We'll move all of the plot construction into the d3.sonar file, plus resizing. So, hopefully we won't need to take any code from 1) - and we'll just be calling the API exposed by 2).
All of the variables and constants will need to be put into the correct file aswell.
I guess these will be the methods that get exposed by d3,sonar file:
createPlot()
addDetection()
addHeading()
addSelectionListener()
I may well be missing things, you are welcome to correct me.
Ashish, I think now is the time to conduct a final refactoring of the control.
I think this should be the strategy:
1). the sonar-d.html will contain all of the test data & functionality, plus the html skeleton 2). the d3.sonar.js file will contain the code that will get used in my project
So, all the code to do with random numbers will be in 1). We'll move all of the plot construction into the d3.sonar file, plus resizing. So, hopefully we won't need to take any code from 1) - and we'll just be calling the API exposed by 2).
All of the variables and constants will need to be put into the correct file aswell.
I guess these will be the methods that get exposed by d3,sonar file:
I may well be missing things, you are welcome to correct me.