Closed mehsan1 closed 3 years ago
Can we changed variable to not be named random as it isn't random but a fixed percentage? That could be very confusing for future developers.
Really like the idea of that click event. Have you tested that in all those frameworks?
I see you use
"header_complex" let header_complex = template_overall["header_complex"]
as a new variable.
and
"is_depth_track" in let is_depth_track = template_overall["is_depth_track"]
as a new variable
and
well_id in let well_id = template_overall["well_id"]
They then need to be included in:
None of these functions are edited to include the new variables.
Taking out lines:
923 & 925 in index.js
.style('overflow-y',"auto")
&
.style('max-height',height_components+"px")
Would disable scroll.. is that intential? .style('max-height',height_components+"px")`
yes remove 923 & 925 in index.js scroll will be handled by front end application
because multiple tracks will need to have one scroll.
I see you use
"header_complex"
let header_complex = template_overall["header_complex"]
as a new variable. and "is_depth_track" inlet is_depth_track = template_overall["is_depth_track"]
as a new variable and well_id inlet well_id = template_overall["well_id"]
They then need to be included in:
- putIncomingSparseJsonIntoPlottingTemplate() function
- getFakeIncomingSparseDataExample() function
- curveBoxTemplateExamples() function
None of these functions are edited to include the new variables.
Ok I will do this and push changes
Also, can we have the default behavior be the depth track is shown?
Right now the depth track doesn't show at all if the depth_track variable is missing. That will confuse new developers. Better behavior is to have it shown by default and only take off if there is a variable that tells it to have that behavior.
Too many complete and partial changes in here....so will close and attempt to reuse some of the improvements later individually
Description