Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display Model and View side by side (configurable) #37

Open
jodator opened this issue Mar 22, 2019 · 2 comments
Open

Display Model and View side by side (configurable) #37

jodator opened this issue Mar 22, 2019 · 2 comments
Labels
domain:dx squad:core Issue to be handled by the Core team. type:feature

Comments

@jodator
Copy link
Contributor

jodator commented Mar 22, 2019

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
idea

@Mgsy Mgsy added this to the backlog milestone Sep 16, 2019
@jodator jodator modified the milestones: backlog, nice-to-have Aug 26, 2020
@jodator
Copy link
Contributor Author

jodator commented Sep 17, 2020

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).

@oleq
Copy link
Member

oleq commented Sep 21, 2020

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,
    • we don't even have time to address crashes like this one Mention in the initial content throws error #98...
    • 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)
  • without full tests coverage, it's basically a suicide mission 😅

@Reinmar Reinmar added squad:core Issue to be handled by the Core team. and removed squad:ux labels Sep 27, 2021
@pomek pomek removed this from the nice-to-have milestone Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:dx squad:core Issue to be handled by the Core team. type:feature
Projects
None yet
Development

No branches or pull requests

5 participants