jgd@rsiatl.UUCP (John G. DeArmond) (11/20/90)
cpcahil@virtech.uucp (Conor P. Cahill) writes: >Don't know much about Oracle, but for an interface tool Vermont Views is >real good. Good design tool (it will dump interface libraries to be read >by your run-time code, or dump C code so you can twiddle bits), Full range >of control functions from the high menu level to the low before, during >and after field functions (The point is that you have as much control as >you want to use). Connor, Not to sound belligerant but I wonder if you've used the Unix version much. At my last client, we sweated nails with it. It works BUT... The biggest problem is that it do not work through curses and instead they invented a "better idea". You are pretty much stuck with vt100/ansi terminals and the AT386 terminal as implemented in ISC Unix 2.2 does NOT work. The screen splatters enough to not be readable. Plus the screen update is not smart so you end up with really slow screens over communications lines. I gave up on trying to use VV on the console of our Compaq development system and used NCSA Telnet over ethernet which worked pretty well. I'm still looking for a high level screen interface library and editor that works through curses or at least knows how to use a standard terminfo. John -- John De Armond, WD4OQC | "Purveyors of Performance Products Rapid Deployment System, Inc. | to the Trade " (tm) Marietta, Ga | {emory,uunet}!rsiatl!jgd | "Vote early, Vote often"
chip@tct.uucp (Chip Salzenberg) (11/22/90)
[ Followups to comp.unix.sysv386 ] According to jgd@rsiatl.UUCP (John G. DeArmond): >It do not work through curses and instead they invented a "better idea". This complaint is valid. Why invent /etc/vvtermcap when /etc/termcap is 90% of what you need? Although that last 10% includes most of the neat display features, like color escape codes. >You are pretty much stuck with vt100/ansi terminals and the AT386 >terminal as implemented in ISC Unix 2.2 does NOT work. These complaints are unfounded. We use VV under SCO Unix, and I've used it under SCO Xenix, and the console is in fact the place where it works best. And if the behavior isn't right for a given terminal, just edit /etc/vvtermcap; no biggy. >Plus the screen update is not smart so you end up with really slow >screens over communications lines. Yes. I wonder about programmers who clear the screen by displaying 2000 spaces! No, I take that back -- I don't wonder about them. I worry that they might be writing nuclear power plant software next. -- Chip Salzenberg at Teltronics/TCT <chip@tct.uucp>, <uunet!pdn!tct!chip> "I've been cranky ever since my comp.unix.wizards was removed by that evil Chip Salzenberg." -- John F. Haugh II