On Wed, 30 May 2007, John Summerfield wrote:
> There are 48 or so combinations of ALT-keys that are usable, and 48 or
> so combinations of cntrl-keys that are usable, and then some programs
> distinguish between left-alt and right-alt giving yet another 48 or so
> combinations of keys, and so far we've not counted keys associated with
> special characters such as ;:[]{} (some of which are used), or PgUp,
> PgDn (some of which are used) etc etc.
>
> How does one get a 3270 to generate these?
Don't. Excellent question, John, and the answer is that you don't.
Don't worry about Alt keys or Ctrl keys.
Simply use what the 3270 can do and build your menus and dialogues
from that. And then there's "navigation". (see <ESC>[H sequences)
On an 'xterm', pressing F1 delivers an <ESC>[224z sequence.
One way to get full-screen 3270 interaction to ASCII apps
is to have the 3270 PF1 AID converted to an <ESC>[224z sequence.
Textual input can be simplified: If the user entered something
without "navigation", the 3270 returns that text and a NL.
If they navigated, then text entered is prefixed with
Escape
[
row
semicolon
column
H
which an ASCII app can interpret as easily as the <ESC>[224z
generated by the ubiquitous 'xterm'.
This is completely within reach.
> It would be possible to write block-mode applications for Linux, but
> current interactive programs expect keys to be presented asynchronously.
Actually, current applications simply lack the needed extensions
to handle block-mode inbound navigation. It's not so much synch/asynch
as it is that they don't deal with a mapped display both ways.
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
