7 Commits

Author SHA1 Message Date
Tim Wojtaszek
f07c09d092 Add png files for svg files due to github hosting issues 2019-08-22 13:20:30 -07:00
Timothy Wojtaszek
4edc9da21c
Fix XVIZ Source doc reference 2019-08-21 13:49:56 -07:00
Timothy Wojtaszek
972968687a
@xviz/ros module (#482)
Support for converter ROS Bag data into XVIZ

Key documents are:
 - RFC ./dev-docs/005-ros-module-rfc.md
 - User Docs ./docs/api-reference/ros
 - Module Readme ./modules/ros/README.md
 - Examples ./examples/converters/ros ./examples/converters/ros-custom
2019-07-02 05:38:00 -04:00
Timothy Wojtaszek
a8cfc2bc29
Change specification enumerations to ALLCAPS (#477)
Follow the convention that constant enumerated values should be in ALLCAPS. This is a spec change for XVIZ, but retains compatibility with lowercase by forcing a case conversion at the appropriate places within the modules.

Spec change locations:
declarative ui properties
- component type
- layout
- interactions

xviz message
- type
  - xviz/start
    - session_type
    - message_format
    - log
  - xviz/metadata
    - stream metadata
      - category
      - scalar type, for time_series & variables
      - primitive type, for time_series & variables 
      - annotation_type, for annotations
    - stream style
      - text_anchor
      - text_baseline
  - xviz/state_update
    - update_type
  - xviz/reconfigure
    - update_type
2019-06-07 18:42:09 -04:00
Timothy Wojtaszek
3a85736550
Change use of 'Frame' to 'Message' in XVIZ (#467)
A 'Frame' is often overloaded, and in nearly all case
in XVIZ we mean an XVIZ Message.  We have created a distinction
where if we use 'Frame' it is not an individual message but the
set of data that constitutes a visual 'Frame' which could come from
multiple messages.  Therefore, 'Frame' is still used in @xviz/parse
2019-05-28 14:30:06 -07:00
Tim Wojtaszek
ed0ba1843a Make sure node related imports can be tree shaken 2019-05-23 16:34:18 -07:00
Tim Wojtaszek
9573a64424 @xviz/io consolidates general reading and writing of the
XVIZ specified data format.

Prior to this functions and classes that operate on XVIZ data
where split across @xviz/builder and @xviz/parser. They will
be moved into @xviz/io in subsequent changes.

Motivation for this is due to @xviz/parser restructuring data that
no longer can be validated against our specification and validation
tooling.  This made it difficult to modify XVIZ and validate it is
still conforming.  Given that, this module should operate only
at the XVIZ specification level.

Highlights of @xviz/io module:
 - XVIZ data classes allow for dealing with XVIZ data regardles
   of the format specifics (binary or json)
 - Abstraction layers keep concerns isolated and provide and improve
   structure for evolving the XVIZ eco-system

Key documents are:
 - RFC ./dev-docs/003-io-module-rfc.md
 - User Docs ./docs/api-reference/io
 - Module Readme ./modules/io/README.md
2019-05-23 16:34:18 -07:00