Collaboration efforts

[kbrock]

I saw that you reached out to black-screen about using terminal.js. This is great. Have you had any other successful dialogs with other js browser terminal implementations? Or are the needs of these various projects really that much different?

Also, could you list the implementations that use your terminal.js or have similar ones?
Does it make sense to extract that portion into it's own node module?

I found a number of terminals that looked semi-recent, but I'm sure you're more aware of the landscape:

• [block-screen] - you already reached out
• chrome hterm src: hterm alt
• shellinabox
• terminaljs
• jquery.terminal
• term.js
• atom term2

Thanks for the great project

[PerBothner]

It's difficult to get any well-established project to replace part of their working code with some alpha-quality third-party dependency. At best they would ask "show us a working prototype". That means I'd have to learn how the other projects, their tools, and make sure DomTerm works as least as well as what they have. And DomTerm is only a small part of what I do.

This is where it would be great to have someone who could help with this.

Atom/term2 seems like an obvious match. If they want to be a next-generation Emacs, then having a next-generation terminal-emulator and shell mode seems a natural fit. I'd love to help if anyone want to tackle this, but myself I have no experience with Atom, node,js, and that ecosystem - and I don't see how I can spare the time.

[PerBothner]

I did also contact Ramalingam Saravanan, author of GraphTerm and the late lamented XMLTerm. He was supportive, but he doesn't have much time for GraphTerm, and I'm not much of a Python person. (GraphTerm is very Python-focused.) When I need a break, maybe I'll take another look.