Add feature: Display Point & RothC output

[shubhamkarande13]

Description

Displays the received Point and RothC outputs as a grid/spreadsheet.

Introducing RevoGrid for rendering the outputs as a spreadsheet.

Point-RothC-spreadsheet.mp4

[aornugent]

Great start! I'm interested to see it with real data. 💯

[shubhamkarande13]

@aornugent I've noticed that point.results and rothc.results point to the exact same variable results in the store, and hence when I run the Point module, the RothC result also gets updated. So the modular approach of the state is just for readability, and doesn't actually isolate all the different variables.
Can we go back to using different names for all state variables?

[shubhamkarande13]

@waridrox could you please test to check if the configuration is broken or not? Everything seems fine at my end.

[shubhamkarande13]

Please have a look at the feature demo in the first comment!

[aornugent]

Great work @shubhamkarande13! A few thoughts:

• that's disappointing our module namespacing isn't working correctly. It might be that we need to be more selective about how we load the Vuex modules. They should be tied to specific components rather than loaded into the global namespace. Please file an issue describing how the code works now and how it's intended to work. Then we have a space to research the problem more fully before implementing a fix.
• the table is a little hard to read, it probably needs a white background and some borders. It's unusual to have it take up the whole page for just a few columns. Again, if you're not interested in fixing it in this PR, then leave a comment on Add a table component #4 for future reference.
• somehow your GCBM changes on add feature: create new GCBM job! #54 have made it into this PR, please remove them.

[shubhamkarande13]

@aornugent could you please review the PR once again? I tried to drop the GCBM job commit from this branch. 😅

@waridrox could you please beautify the tables a bit as suggested by @aornugent ? I'm bad at design. 😂

Thank you both! 🤗♥️

[waridrox]

Here's the preview for modified implementation. The state updation from vuex could be referenced later, though it is a crucial thing to worry about 😕 - https://michaelnthiessen.com/debugging-guide-why-your-component-isnt-updating/

graph-demo.mov

[aornugent]

@waridrox - agreed, it's important. I like the mapState pattern in the link you shared above. I believe this can be used to handle modules that share similar names by setting namepace: true, as described here:

https://laracasts.com/discuss/channels/vue/vuex-actions-with-same-name-in-different-modules?page=0

But I don't yet understand why we have conflict given that our modules are isolated within components.

Is it true that store/point.js is only loaded in point components (and store/rothc.js is only loaded in rothc components) or are they being invoked at a higher level that causes a namespace collison?

This PR is looking good for now, so let's file an issue to continue the namespace discussion after we merge.