The Space Console
- bert
- Kyle (Unlicensed)
The Space Analyzer gives access to a lot of advanced features for observing/inspecting/altering a given Space.
You can access the Space Analyzer from the Space’s Page.
The Space Analyzer has several pages which can be navigated to via the bar on the right of the screen. You start with the Space Details page open.
Space Details
This contains some basic info about the Space and it’s members. It will also tell you which members are currently connected to the space. (Note: being in the Space Analyzer “counts” as being connected.) The Local User panel, meanwhile, describes you (the user in the management console) who will potentially be making changes to the space.
Participants
This page describes all the current Connections to the space. Note that Connections differs from Members, in that a single Member may or may not be connected, and they could be connected multiple times on multiple devices. This user is connected both via the Space Analyzer and via an Application. This list is live, so as people join/leave it will update.
Properties
The most powerful use for the Space Analyzer is that it gives you the ability to modify Properties inside a Cavrnus Space. A Property is simply a piece of data that exists at a given path. It forms the basis for all Cavrnus Data Synchronization, and is used by things like, say the No-Code Components to synchronize the position/state of objects between clients. When clients post changes to property values, they will show up in this page. Moreover, when you change them on this page they will show up in the clients.
The above chess piece’s transform value would correspond to a component in your application with the following setup:
Cavrnus supports various types of Properties, including Strings, Bools, Floats, Transforms, Vectors, and Colors.
Live Journal
This page gives you a complete history of everything that was ever done in a space, and by whom.
The bottom of the page contains a “scrubber”, showing activity in the Space. (Note that “activity” here means changes posted to the journal, which doesn’t necessarily include users connecting and looking around, but not making many changes).
