Currently the reactivData is using the first inputs to determine the outputs. The problem is, that this is getting very intransparent which inputs it really dependend on. Why should the graph calculation bother if input$selected_vj changed if the scope of method only knows about the array and thus using that as a reactive component should help.
The other problem is, that changing an input will trigger a new computation. Therefore isolate is there. That way, we can trigger the recalculation upon button click; in our case the plot network, plot community, plot degree distribution. Doing that we get a more modular design and can add more buttons or in-between logic easily.
Currently the
reactivData
is using the first inputs to determine the outputs. The problem is, that this is getting very intransparent which inputs it really dependend on. Why should the graph calculation bother ifinput$selected_vj
changed if the scope of method only knows about thearray
and thus using that as a reactive component should help.The other problem is, that changing an input will trigger a new computation. Therefore
isolate
is there. That way, we can trigger the recalculation upon button click; in our case the plot network, plot community, plot degree distribution. Doing that we get a more modular design and can add more buttons or in-between logic easily.