Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!olivea!genie!udel!princeton!njsmu!mccc!dworkin!shevett
From: shevett@dworkin.UUCP ( Sysop)
Newsgroups: comp.databases
Subject: Re: Foxpro on SCO Xenix
Message-ID: <55@dworkin.UUCP>
Date: 30 Jun 91 22:12:45 GMT
References: <1991Jun20.182306.26927@ucunix.san.uc.edu> <79012@brunix.UUCP> <53@dworkin.UUCP> <227@ahmcs.mq.com>
Lines: 82

alan@ahmcs.mq.com (Alan Mintz) writes:

>In article <53@dworkin.UUCP>, shevett@dworkin.UUCP ( Sysop) writes:
>) fred@compu.com (Fred Rump) writes:
>) >shevett@dworkin.UUCP ( Sysop) writes:
>) 
>) Under Xenix, there is no way to trap more key definitions than those 
>) allowed under the termcap.  Our DOS systems use Up,Down,Left,Right,Home,
>) End,PageUp,PageDown, and all 10 function keys.  We can't trap those
>) keys in a meaningful way under Xenix.  It just can't do it.

>To be more accurate, it takes more code to trap these keys. 

Theree are two ways keystrokes can be trapped into SCO Foxbase:

	Readkey() - which returns what pre-defined key was pressed to exit
		a read function, and

	inkey() - which returns the actual ascii definition received by the
		program.

Using inkey(), you can make your system react to any sequence the terminal
throw at you, simply by trapping the entire escape sequence.  Likewise,
with readkey(), you may trap any COMPLEX string sent to the applciation,
and Foxbase will translate into one of the following pre-defined
sequences:

	Up		Down		Left		Right
	PgUp		PgDn		CtrlLeft	CtrlRight
	F1-F10		Insert		Delete

Our applications need many more keystrokes, such as Home and End,
Shift and Control versions of the function keys, etc.  We could write
our own handler for these functions, that would translate ESC-BlahBlah
into a Shift-F7, but the program would not be portable across
different terminals.  

>Using SCO Foxbase+
>and the INKEY() function, we have done a number of unusual things like

[Various neato functions that FoxBase cannot do included]

We too have done these under FoxBase for DOS, using inkey(), translated
to Function Keys and other keys.  We have written an interactive
BROWSE function to replace the brain-dead BROWSE in SCO Foxbase, but it
is very keyboard specific.

[Comments about lack of Video/Keyboard operations under Foxbase, while
WordPerfect for Unix does a *wonderful* job of handling odd terminals.]

>What's fancy about using function keys (again - available through SET FUNCTION
>or INKEY())? Admittedly, it would be nice to see support for bold/underline/
>blink and color in the SCO (or future Fox) product. I tried implementing this
>within Fox+, but the (color) sequences I was sending were getting intermingled
>with cursor positioning sequences.

We had this problem also, but again you end up writing an application that
is terminal specific.

(A thought comes to mind we played with - making a TERMCAP like system
for FoxBase, but this requires using, yech, macros.  Bleh - slow down city.

>) The problem is we need to port an application that is already running 
>) under DOS with a *very* specific user interface to Unix.  We need the 
>) advanced video and keyboard functions.

>Then wait for Foxpro/*NIX (1Q92). It is reasonable to presume that they will
>allow color support on terminals that support color. The point is, it is
>possible to develop dynamic, "pretty", user-friendly applications using
>the existing product - it just takes more work.

I agree with the 'more work' department.  I think it's too difficult to 
maintain a DOS product, then realistically port it to Unix, giving up 
so much to make the port.  I can't *WAIT* to see FoxPro for unix.  (Fact
of the matter is, I can't wait to see FoxPro 2.0 for DOS!

>< Alan H. Mintz  | alan@ahmcs.mq.com | ...!uunet!ahmcs!alan >

--------------------------------------------------------------------
shevett@dworkin.amber.mccc.edu | Dave Shevett - Lawrenceville, NJ
CSAccess BBS (609) 584-8774    | Keeper of yon FoxPro mailing list
--------------------------------------------------------------------