4 ms·
This is an excellent idea, it is a bit hard to use though. Some thoughts. I would prefer breakpoints to be disctinct from the current execution position. Wh
by Lerc 7y ago
This is an excellent idea, it is a bit hard to use though.
Some thoughts.
I would prefer breakpoints to be disctinct from the current execution position.
When thinking analogously to a debugger, Breakpoints indicate where the program should stop not where the program currently is, and consequently breakpoints can exist on multiple lines at once.
I prefer a different graphic to indicate the active line. A line highlighted colour would be enough
On my machine the area that is active for the 'line annotations' pop-up menu has no visual cue to say that it is there.
It appears to crete a new 'line annotations' menu for each hover with the old menu lingering a short time before dissapearing, this looks quite odd.
I have achieved multiple perminantly open 'line annotations' menus at the same time.
It would be beneficial to have line ranges on annotations so you can higlight a block of code.
Adding a new frame duplicating the current annotations would be good. Either that or have a way to declare the same annotation applies to multiple frames.
Having the ability for an annotation to collapse a section of code to ... for within a single line or \n...\n for multi line collapse would let people focus on the code being explained.
- vidoss 7y agoGreat feedback. Moving this line by line to my TODO. Thanks again.
- vidoss 7y agobtw, was the editor intuitive to use? I am thinking of adding product tour like popups on that page to get started.
- Lerc 7y agoI figured it out easily enough, adding annotations and removing them was understandable enough, what the annotations did was a bit trickier but I think documentation would be better than a tour. A reference gallery showing what each one does would be ideal.