References: <3D9A6307.1040800@BOGUS.earthlink.net> <_FEm9.97658$S32.firstname.lastname@example.org> <3D9B22E2.email@example.com>
Subject: Re: Anyone using Spice OPUS?
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
Date: Thu, 03 Oct 2002 16:23:51 GMT
NNTP-Posting-Date: Thu, 03 Oct 2002 12:23:51 EDT
Organization: Cox Communications
"Christopher R. Carlen" wrote in message
> Mike wrote:
> > "Chris Carlen" wrote in message
> > news:3D9A6307.1040800@BOGUS.earthlink.net...
> >> Hi:
> >> ... I hated the Berkeley SPICE too, because it didn't have command
> >> line editing, which any respectable modern program ought to have at
> >> least, if it dares to be a CLI program in the first place.
> > SPICE has been a CLI program since its inception (maybe before your
> > conception?), long before the advent of cheap terminals that could
> > display anything more than ASCII.
> No, what I'm talking about is editing the commands on the command line,
> like a modern shell such as Bash can do.
Got me there. I only run SPICE in batch mode, not interactively.
Adding an edit window is fairly easy in Windows, and I suspect it's also
relatively easy in X if you use one of the toolkits (gtk, Qt, etc). The main
problem is probably (I'm guessing here) that the SPICE you're running is a
console application, not an X app. Still, converting it might be the easiest
way to do what you want without having to write your own interface from
scratch. My experience with Windows is dated, but I was able to build a
"command line application" that opened its own edit window and processed
commands from there. All the basic editing functionality (copy, paste,
delete, insert, overstrike, etc.) was included in the edit window; all I had
to do was instantiate the window, then add hooks for the keystrokes I wanted
to process. One nice thing about this approach was that things like menus
and file open/close/save dialogs were pretty much free. Another nice thing
is that the keystroke trapping interface was well defined and easy to
implement. The programming overhead to implement the "CLI" was actually
quite small - I started with an example program Borland provided, and made
minor modifications over the course of an evening. The executable overhead
was somewhat higher, but it wasn't a bad trade-off: I generated a basic
command line environment in one evening, with only a little coding.
In the case of SPICE, the task could be almost as simple, or it could be
much messier, depending on how well the code is partitioned. If you can
replace the edit functionality as a block, and if the gtk/qt/??? libraries
have something analagous to the edit window, then it shouldn't be a terribly
-- Mike --