-
Notifications
You must be signed in to change notification settings - Fork 15
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
Idea: In-console visualizations #29
Comments
I am definitely interested. I was already looking into it, when I thought about exposing Ruby object properties as hierarchical trees (maybe by embedding Firefox's lazy loading object trees and implementing REPS protocol, but that single feature would have multiplied this extension's code). It would not be too difficult to hard-code a single new visualization type in addition to the existing ones, but in the long-term I need to figure out an interface to make it extendible with more visualizations without blowing up the code. |
Can you point me to where I'd start in trying to add such a prototype visualizer? Would it be in Ruby or JS? |
The interactivity is added client-side in JavaScript, after tokenization and highlighting (with Ace's highlighter). So the output is already split into colorized HTML tags and annotated with CSS classes depending on the type of token. Look into feature_highlight_entity.js.
|
I was doing some improvements to my Transformation Inspector and I got an idea for Console Plus I wanted to run by you:
Allowing return value lines to have visualization widgets in-line in the console. This wouldn't be far off from the visualization already done for vectors etc in the viewport.
Some things like Transformations can't be visualized in the viewport, but it would be nice to bring up a better view of it in the console. For example:
This could also be extended to other things, for instance:
An array of points. The console widget could be expanded to some options:
Would be very useful for visually debugging and experimenting.
Is this something you'd be interested to feature in this extension? Would you accept PR for this?
The text was updated successfully, but these errors were encountered: