Roadmap Q1 2021

[alexrobin]

• [x] Rename Json datareceiver as SweJson
• [x] Completely remove deprecated data sources (Chart.js, EulerOrientation, LatLonAlt, UAHWeather); Use SweJsonDataSource datasource in all examples instead
• [x] Move some data sources and stylers to ext (OrientationQuaternion.js, Nexrad.js (both datasource and styler))
• [x] Refactor folder structure (source/osh; source/osh-ext; source/osh-vuejs)
• [x] Fixed buffering/synchronization logic
• [ ] Implement layer on top of data sources to avoid declaring the same offering multiple times (see Nick work in osh-client, add to Entity object?)
• [x] Generic action callbacks (for entities and view items)
  • [x] Design
  • [x] Implementation
• [x] Add support for batch historical obs requests
• [x] Add GetFeatureOfInterest data source
• [ ] Generic reusable vue.js components on top of our views
  • [x] TimeController
  • [ ] DraggableView
  • [ ] DockedViews
  • [ ] StackedViews
  • [ ] DraggableStackedViews
  • [ ] ViewWithControlDrawer
• [x] SensorWeb API client
  • [x] Design
  • [x] HTTP implementation
  • [x] MQTT/WS implementation
• [ ] Improve Tasking
  • [ ] SPS client
  • [ ] Auto generate generic form from tasking parameters (either SPS or STA)
  • [ ] Support websocket for command streams
• [ ] STA client
  • [ ] Design
  • [ ] HTTP implementation
  • [ ] MQTT implementation
• [ ] Generic binary data source -> present as JSON object with fields as ArrayBuffers when it makes sense (e.g. large numerical arrays, compressed data such as video frames)

Do we even need a model for action callbacks? Should it be a pure UI thing? -> Can be useful in a multi-view environment where consistent action handling is needed across views (e.g. same behavior no matter where the item is selected), but it could still be handled at the UI level.

Actions = hover, left click, left double click, right click, drag, tap etc. so just forward UI event + entity/viewItem/dataSource info, or higher level events like select/show/hide/menu?