webViz issueshttps://gitlab.ub.uni-bielefeld.de/scs/webviz/-/issues2021-10-15T18:52:31+02:00https://gitlab.ub.uni-bielefeld.de/scs/webviz/-/issues/4To checkout2021-10-15T18:52:31+02:00Jan PöppelTo checkoutI have found Visdom (https://github.com/fossasia/visdom) which could contain valuable aspects we may want to take a look at, or just switch to using completely.I have found Visdom (https://github.com/fossasia/visdom) which could contain valuable aspects we may want to take a look at, or just switch to using completely.https://gitlab.ub.uni-bielefeld.de/scs/webviz/-/issues/2Improve documentation2018-11-22T15:30:41+01:00Jan PöppelImprove documentationIf the tool should be used going forward, it should be documented appropriately.
The readme should at the very least include:
* Descriptions of all components
* This includes description of available configuration and made assumpti...If the tool should be used going forward, it should be documented appropriately.
The readme should at the very least include:
* Descriptions of all components
* This includes description of available configuration and made assumptions regarding data structure
* Improved/more suitable example images once the tool has become more finalized in its appearance.
* A basic example of how to add new components
* This needs to include information about how the config Information needs to be structured
* Some reference to how the communication with the redux store works.
* This should include how the store is organized.https://gitlab.ub.uni-bielefeld.de/scs/webviz/-/issues/1General Feature Wishlist2019-07-01T11:41:14+02:00Jan PöppelGeneral Feature WishlistThis is a general issue to collect ideas for features we might want to add. Anybody can suggest a new feature here. If we decide to develop a specific feature, it can get its own issue.
* [x] nested DataKeys
* Hiding of configuration di...This is a general issue to collect ideas for features we might want to add. Anybody can suggest a new feature here. If we decide to develop a specific feature, it can get its own issue.
* [x] nested DataKeys
* Hiding of configuration dialogs
* Preview/demo for available modules, e.g. with dummy data
* (Maybe open Issue at ReactGridLayout): When resizing components, move others not only down, but also right, as long as there is space
* Allow probing for available connections and display data send over these connections
*
* Automatic discovery and compilation of new components/modules
* Consider hosting (compiled) modules as their separate .js files somewhere, e.g. as a growing catalogue. Would reduce size of the main framework (especially when considering dummy data for previews)
* Somewhere can actually be local and we "host" the different modules on a different "endpoint"