Full Screen Editor

The main reason to have it written in Ruby was for ease of integration into
the rest of the program. I’m not sure how to pass the socket IO to an
external program and back…

Mark

From: Matt Gushee [SMTP:mgushee@havenrock.com]
Sent: 11 September 2002 18:46
To: ruby-talk@ruby-lang.org
Subject: Re: Full Screen Editor

Ah, but I want to connect this to the Ruby BBS program that I wrote,
so that
users on the other end of a telnet connection can use it to edit their
messages…

No idea how to even think about going about that…

If the main requirement is exchanging text over telnet, then shouldn’t
you be looking for an editor that will interact with telnet? Many

Uh, scratch that. I wasn’t thinking clearly. But I think I see what you
mean now: people log into the BBS server through Telnet, and will need
to use an editor that runs in the Telnet window, right?

I still don’t think you need to limit yourself to an editor written in
Ruby. First of all, I would guess there isn’t one. But even if there is,
it’s unlikely to be as good as Emacs, VI, Pico, etc. That’s not meant to
disparage Ruby, but writing a good text editor is a lot of work, and
Emacs has been under development for at least 15 years, VI even longer.
So why don’t you give your BBS program a generic interface
(socket-based, shell-based, I don’t know, but probably one of the two)
so that people can use any of several editors to interface with it? That
way, your users get a good text editor, and you don’t have to create it.


Matt Gushee
Englewood, Colorado, USA
mgushee@havenrock.com
http://www.havenrock.com/

NOTICE: This e-mail and any attachment(s) may contain confidential and
proprietary information of Goss International Corporation and/or its
subsidiaries and may be legally privileged. This e-mail is intended solely
for the addressee. If you are not the addressee, dissemination, copying or
other use of this e-mail or any of its content is strictly prohibited and
may be unlawful. If you are not the intended recipient please inform the
sender immediately and destroy the e-mail and any copies. All liability for
viruses is excluded to the fullest extent permitted by law. Any views
expressed in this message are those of the individual sender. No contract
may be construed by this e-mail.

···

-----Original Message-----
On Thu, Sep 12, 2002 at 02:32:23AM +0900, Matt Gushee wrote:

On Thu, Sep 12, 2002 at 01:07:00AM +0900, Firestone, Mark - Technical > Support wrote:

I see … well, Emacs lisp has library functions for sockets, I’m pretty
sure. I won’t say it’s easy to program with them, but certainly doable.
Other editors … now that I think of it, I suspect most other editors
can’t do sockets, but Vi and its clones and probably a whole lot of
others can certainly interact via shell commands, using pipes or FIFOs.

However, there is the security thing Dossy brought up … sigh … I
hate security. The world would be so much simpler without it.

···

On Thu, Sep 12, 2002 at 07:45:20AM +0900, Firestone, Mark - Technical Support wrote:

The main reason to have it written in Ruby was for ease of integration into
the rest of the program. I’m not sure how to pass the socket IO to an
external program and back…


Matt Gushee
Englewood, Colorado, USA
mgushee@havenrock.com