Report this content

Yes, I've been programming for years. "Self-commenting code" is something akin to naming gadgets, I think. For me, most of the time I don't make text notes beyond that for myself or even others to use the logic. I just lay things out and name gadgets in a way that makes it easy to understand what things do.

Personally I feel like the convention of using a powered-off "big" text gadget as a developer's comment is pretty ubiquitous at this point. Started back in beta, and people are still using it this way. Any time I see an unpowered big text gadget, I know it's a comment. For any real text, it would not be turned off (or would have something wired into it), so that's how I tell the difference.

Also with the text gadget a user can hover over it and see the full text on the screen--so if you prefer you can make the gadget small and the user can still read a lengthy comment just by hovering.

Another thing we could do once the change goes live is, changing the colour of the text gadget itself. We used to be able to do this in beta, but things were changed. I believe they have plans putting that feature back, as it's very useful for colour coding. And in this case, could be used to further differentiate it as a "comment."

I think personally, a "comment"/"note" gadget would be so amazingly close to a text gadget it's not even worth making a distinction. Perhaps the text gadget could be expanded on to fit what you're thinking of, and it would save developing a whole new gadget and UI and QA-ing it all from the ground-up.

A note would also use thermo by the way; it wouldn't be thermo-free. If it's saved with the creation, and there in edit mode... it uses memory and thermo to be there.