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
Since we've been talking about adding a feature to show the respective source knitout lines of code alongside each output kcode pass for debugging, I was thinking the html webpage could be a good place to do that.
Maybe in a live visualizer kind of fashion—where you can toggle the visibility of the source knitout and either:
clicking on the lines of code for a kcode pass highlights & scrolls to the corresponding knitout (& vice versa)
or the kcode is labeled with the line numbers for the corresponding knitout (and vice versa)
The text was updated successfully, but these errors were encountered:
I have been viewing the index.html as a way for folks to try things out before diving in deeper, which means the primary design goal is to make it uncomplicated and clear to a first-time user. This means -- from my viewpoint -- eliminating clutter (possibly including any display of input or output files).
So I think that this enhancement -- while useful -- doesn't belong in index.html .
alright, that makes sense to me. maybe we add a separate html file that is for debugging/has more advanced features?
gabrielle-ohlson
changed the title
adding knitout-to-kcode comparison feature to index.html
adding knitout-to-kcode comparison feature to html file
Feb 27, 2021
Since we've been talking about adding a feature to show the respective source knitout lines of code alongside each output kcode pass for debugging, I was thinking the html webpage could be a good place to do that.
Maybe in a live visualizer kind of fashion—where you can toggle the visibility of the source knitout and either:
The text was updated successfully, but these errors were encountered: