You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2021. It is now read-only.
The core idea behind this is that we should be able to have multiple views on a particular data set, for example, a unit, without having to care as much about syncing them up. KeyValues view, Object view, and so on can all just be interpreted as different interpretations of an underlying dataset. Instead of having them actually have different data sets, they should, as close to the actual interface as possible, share the data, so that updating one updates the others (in real time, if possible (and it's possible)). This also gives benefits later on; with the goals in some other issues of having better auto-suggest for various things, or automatic analysis of code, having a more readily workable data representation would be beneficial.
@Penguinwizzard mentioned doing this. Investigate it's viability and how much it would take to break them apart.
The text was updated successfully, but these errors were encountered: