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

Smarter rendering of data structure width #123

Open
danielcompton opened this issue Dec 7, 2017 · 2 comments
Open

Smarter rendering of data structure width #123

danielcompton opened this issue Dec 7, 2017 · 2 comments

Comments

@danielcompton
Copy link
Contributor

When we render data structures, we sometimes render too widely and people need to scroll sideways to see more. Other times we don't render widely enough (e.g. pop-out panel on a widescreen monitor) and we 'waste' space.

Dirac's rendering config renders based on counts of items in collections. Over certain thresholds they are elided and you can use the dropdown arrow to show more. It would be great to be able to calculate the width of a rendered data structure line, and choose the best way to lay it out, while still staying within the boundary.

@agzam
Copy link

agzam commented Jan 19, 2018

I second that. In our app we use a lot of namespaced keywords in the app-db, and sometimes nesting is a bit out of hand. And narrowing down to the exact place in the state is right now kinda difficult (even compared to re-frisk). Would be nice maybe if the input supported autocomplete. But that probably still wouldn't completely solve the problem.

@danielcompton danielcompton changed the title Smarter rendering of data structures Smarter rendering of data structure width Feb 9, 2018
@kimo-k
Copy link
Contributor

kimo-k commented Jun 16, 2023

Would be nice to render namespaced keywords with an expander or tooltip when they're longer than a certain length. Also, consider a way to declare ns-aliases in the settings, or even get them from the source code somehow.

As for tweaking the layout based on the rendered size, sounds non-trivial. Maybe you'd implement that in jsonml->hiccup somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants