# \[ANNOUNCE\]node-red-contrib-xterm : second beta (sidebar)

**URL:** <https://discourse.nodered.org/t/announce-node-red-contrib-xterm-second-beta-sidebar/19718>\
**Category:** Share Your Nodes\
**Created:** [30 December 2019 00:16 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-xterm-second-beta-sidebar/19718 "2019-12-30T00:16:47Z")\
**Posts on this page:** 1\
**Showing post:** 85

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [7 January 2020 20:59 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-xterm-second-beta-sidebar/19718/85 "2020-01-07T20:59:15Z")

</div>

> [@edorgeville](#):
>
> your work could be ported to make a dashboard widget

Hi Erwin (@edorgeville),  
Although it might seem very similar, there are a lot of changes required:

- Dashboard UI node instead of sidebar panel.
- AngularJs instead of jQuery
- RED.httpNode instead of RED.httpAdmin node.
- Flow editor and dashboard use other websocket libraries
- Since the RED.httpNode [doesn't](https://discourse.nodered.org/t/red-httpnode-get-gives-unauthorized/8749/2) accept RED.auth.needsPermission, I'm not sure how secure it is? Might be no problem, but I don't know ...
- Currently the sidebar panel ensures that always a single Terminal config node exists. Not clear to me how you would manage the terminal settings in a UI node (since you don't have a sidebar tabsheet then).
- And so on ...

Of course everything is possible, but at first sight it probably needs to be build from scratch...  
But you have the advantage that you can start from my current code. Good luck with it!

Bart

---

_[View the full topic](https://discourse.nodered.org/t/announce-node-red-contrib-xterm-second-beta-sidebar/19718)._