search

f / term.coffee

Terminal Client written in CoffeeScript
MIT License
0 stars 0 forks source link

Battle plan #1

Open abe33 opened 10 years ago

abe33 commented 10 years ago

I was wondering how do you plan to port term.js.

At first I thought we should have started by splitting the term.js file into several js files, then adding the concatenation process and then progressively converting the files from js to coffee. It would have been more progressive.

How do you see the work here?

f commented 10 years ago

I'm planning to rewrite (port) pty.coffee at first. And then I'm going to rewrite (port) term.coffee. PTY does the hard work and needs hard work. We won't touch C parts (I'm not good at C). We'll just "tidy up" all the code and rewrite with CoffeeScript. And I'm going to use Grunt instead of oldie Makefile.

After porting it to the CoffeeScript, let's work hard on Term.js and rewrite all the client. It'll be easier to maintain (at least for me).

What do you think about this plan?

Edit: We can do your process for both projects. Seems good. :+1:

abe33 commented 10 years ago

Sounds good to me, I must say that I didn't dug much in pty so I'm not sure what it does, so I'll follow you on that. Let me know what I can do to help on pty at the moment.

f commented 10 years ago

pty.js is psuedo terminal. Term.js opens pty.js process init and basically parses the results.

https://github.com/chjj/term.js/blob/master/example/index.js#L37

f commented 10 years ago

I mean term.js is like a shell on pty.js.