-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repo inactivity #47
Comments
@chjj are you interested in help maintaining this project here, or should an enterprising user start a new fork? |
I have a lot on my plate as of late. There's nothing that says someone can't fork this. This weekend I made a promise to myself to go through my personal projects and examine PRs. I'm very sorry I've been neglecting this. My next goal with this project was to get it working well with android, but I gave up after an hour or two. I will go through my projects this weekend. |
Also, if someone wants to become a collaborator, I would sort of like a demonstration of low-level terminal knowledge first. I'm sorry for it to be so meritocractic, but that's the way I feel. I wouldn't trust someone working on this unless they know what they're doing with terminals. I'm sure there are a lot of people out there who do. That is, unless they want to do something un-terminal related, like get it working well in android and so on. |
@chjj you don't have to apologize, it was not my intention to accuse you of anything. The only reason I opened this ticket was to suggest setting a new fork as the main repo of this project, because it seemed like other developers have embraced it (judging by the PRs). I guess finding some collaborators to help you out would be a better idea. |
No worries, it's the burden of having personal projects become popular. We appreciate your work (IPython already uses marked and is picking up term.js). Hopefully someone qualified can come help out. |
Many moons have passed.. any news about the future of this project? Looking at the fork history and pull requests, people are forking to add minor platform specific fixes. Would be cool if they land back to upstream and up to npm. Any idea when 0.0.5 release could happen? 🎱 :) |
We're using term.js in IPython (with a Python backend I maintain), so we could try to co-ordinate the activity around the project and bring people's different fixes together, if that would be useful. I don't think any of us know enough about terminal emulation to develop something like this, but perhaps we can facilitate things for the people who do. |
I'm not sure if @chjj is silently lurking here (he seems to keep himself busy with other projects) but I'd be super glad if there would be somewhere.. anywhere a proper development branch that would facilitate pull requests and put up with people whining until things are stable again and then.. maybe.. a bigger pull request will be merged to master and released? I'm using term.js with a cloud9v2 fork I maintain (screenshot). However, with the current version of term.js I can't properly type special characters 😱 |
I've been keeping my eye on PRs here and there. There are a number I want to merge. I'll do it tomorrow. I just need to be bugged to remember this stuff. :) I'm also willing to accept others as maintainers and contributors depending on how familiar you are with term.js. |
And yes, I do drift from project to project. Right now it's blessed, and marked and term.js have been neglected. I do want to get back to them. I figure I'll be tentatively satisifed with where blessed is at soon. |
@chjj thanks! It's good to know that this is still on your radar. |
I was just talking to Varun Ganapathi of terminal.com, he mentioned that @zzmp has been doing a lot of work with term.js, and might be able to help out upstream. |
the dCache project is also considering integrating term.js into its web interface in order to provide https access to an administrative shell currently only available via ssh. I have mocked up a prototype using a term.js client and websockets against a Java (Jetty 9) back-end, and it works generally very well, but there a several issues, particularly with cut-and-paste (using the mouse), ctl+a, ctl+e, backslash on European keyboard mappings, and unwanted line breaks when the number of lines written to the terminal force vertical scrolling. I am not a terminal developer, so I, too, would very much like to know if further support for patches/pull-requests on some other fork is currently available. Thank you very much! |
@takluyver we've been doing a lot of work with term.js and tty.js at terminal.com, and could probably help upstream - let me just make sure I can make time before committing to this. @chjj do you want to have a chat about this project? |
@zzmp, yes. You can shoot me an email. I'm happy to add collaborators to the project who are familiar enough with it. |
Also, as of late, although I've been neglecting some PRs, I have been doing more work on term.js: Better parsing for DCS (and anything that requires an ST terminator), tmux DCS passthrough, turning it into a real node-like TTY stream, etc. The next thing I want to do is rip out some of the code in blessed and make it fully headless with the blessed shim. Then, eventually refactor the whole thing so it is platform agnostic with regard to the browser vs. node, and keep the browser code separate. It will still be a browser terminal by default of course, but optionally headless. |
✨ 😸 ✨ |
hi! Some news? |
Seems like the owner hasn't updated the repo since a long time and I could really use a lot of the pull requests that others have opened. Since it's open source, maybe we should consider opening all these PR's into a new fork to make sure everyone gets the so needed updates...
The text was updated successfully, but these errors were encountered: