Linked by Eugenia Loli-Queru on Sun 3rd Sep 2006 12:23 UTC
Thread beginning with comment 158586
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Not really. The problem with having a seperate sidebar is that it wastes screen space. The problem with inline comments is it spaces out code vertically. My solution has all comments to the right of the code, within the same text box, yet it doesn't interfere when writing code. It just serves as commentary.
For example, if you press return after a line with a comment, the comment remains on the line and the cursor moves onto the next, perhaps auto-indenting.
I haven't really thouroughly thought it through.






Member since:
2005-09-11
Hey, I had the same idea - it's very interesting, especially in regards to i18n and image imbedding. I'm afraid that syntax/localized keywords, commands, variables could end up badly - it'd be harder to communicate between programmers, etc. However, maybe there could be chat clients that handle the conversion.
Always pretty printing the code as you like it could be valuable - not actually changing the syntax drastically, but changing the presentation in general could be practical.
You did have an idea I haven't thought of before - variable frequency of comments (pro to beginner). What I had imagined is the comments (including images, doodles, etc) completely seperate from the code, yet attached to it. Not quite in a sidebar, more like along the code yet not part of it. It's hard to describe...