Open comment node in new window

Hi there!

I document within NR using comment nodes. So far, so good.

When I implement something I close my comment node in oder to open (and edit) another node.

I find no way to keep the contents of a comment node visible while juggling with another node.

I can open the debug tab in a new window. I would be great to keep a comment node open while editing othe nodes. That would be super helpful with my weak short term memory.

Or do I miss here something and I can do that already? If so, enlighten me, please.

If not: Do you think this is a good idea and can, should be implemented?

Or: How do you manage to keep information from your comments in your head after you close the comment node …

Cheers, Uwe

i usually open a notepad and do alt+tab between NR and Notepad or keep both windows cascaded. later on copy all the contents from notepad into comment node .

Yeah, this is a possibility However, it looks … clumsy, like a workaround, not smooth. The tool (NR) forces you to do something that could be handled by the tool itself.

1 Like

It is! I built myself a scratchpad node that gives me empty text fields where I can paste stuff temporarily (or save it in the flow). The node or better said plugin, lives in the sidebar so that it never closes.

I might publish it, I've only use it privately because I haven't seen a broader need and also because I didn't want to write documentation for it!

You can try it out over at the serverless Node-RED, it's included in that.

Are you suggesting that the debug node config dialog should have a similar "Open in new window" option?

What about the Description tab of the config dialog for all nodes?

These browser popups would be read-only?

I talk about a requirement (feature):

  • The "properties" of one (or more) comment node(s) shall be visible (as rendered markup) while editing another node.

I don't know anything about how to implement this "visibiity". One first, naive idea was to implement it like the debug tab which can be displayed in a new window, that is: show the rendered markup of a comment node in a new browser window. Perhaps just one comment node in just one new window. Another one in another window, if necessary. When done, close the browser windows with the comment's rendered markup.

I am aware that one can run into problems here: does it fit to NR approach and its UI "rules"? What about showning a comment while editing exactly this comment … ?

I cannot say that if would be wise to add the option "Open in new window" to the whole "Info" tab. I think not. But I think it might be nice to have rendered markup of comments like sticky notes available on the screen (each in a new browser window), just like the debug tab.

Perhaps the Info sidebar could be made to tear off. That would be a start at least. It renders the comments for a node selected in the sidebar.

I don't think it clumsy at all. I do this very thing for most of my sysadmin tasks so it is natural to do the same in NR.

If this gets implemented I hope I can disable it!

Users are different. Like the debug sidebar tab, you should be free to use the feature to detach it and open a new browser window ... or not.

1 Like

I agree. It would be a nice enhancement to duplicate the debug sidebar detach button for comment nodes and node descriptions, if it's not a huge task.

My procedure is to copy and paste into Notepad or a window running vi, so I wouldn't personally use it though :melting_face:

I think the request is not just to detach it, but to keep it open on the original node whilst editing other nodes.

I've often wished I could keep the sidebar help for one node open while I'm editing another. Another place this feature might be handy?

while the help panel does update when ever you edit a different node, you can easily change/view help of any node while editing a different one.

chrome_qqgRoq9xBm

1 Like

Though that is just the generic help for a node type isn't it? Not the description that you may have added to a particular instance of a node.

Blame me. I was just thinking of other places where it might be valuable to have something in a separate browser window.

  • Comment node contents
  • Debug node output (and any new/third party debug nodes)
  • Node description
  • Node help