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
Bumping importance of this. It might not be clear which view element is rendered for which model element. UI elements in the editing view might hinders generic items like <div> (if one wants to convert them).
Having model <-> view side by side could show which element in the view and in the model is selected (ie by synchronized highlighting).
Yeah, I get this would be a great feature. On the flip side:
this is a massive task in the context of the project
it requires changes in the model (data store) of the application because model and view (tabs) would need to be fueled with data at the same time and the current redux store is optimized to have only one at a time,
configurability of key building blocks of the UI adds another layer of complexity to the app; plus on top of it, depending on the configuration, the data store would need to behave one way (data for model and view at the same time) or another (just model or view)
model and view trees are very different (different lengths, depths); when you scroll one, the other must follow and remain in sync (something like Mardkown preview in IDEs) so you know which model item represents which view item and vice-versa
while reading mapping is fairly simple (I hope), integrating it into with scroll sounds like a really challenging task,
not sure if the library we use for flexible columns rendering will support 3 columns (research needed)
Sometimes it is not convenient to switch from model to view views - especially when tracking how some elements in model are rendered in the view.
I'd like to have a view (could be configurable) when both panels are visible, side by side
The text was updated successfully, but these errors were encountered: