Re: Re: TN5250 0.16.2 released! -- LINUX5250

If the product is supposed to emulate a 5250 terminal, I would suggest that
the emulation should cover the whole terminal and not just the display. Maybe
it already does, maybe it's just too poorly documented to get up and running
exactly how people want - as the mailing list archives illustrate? (I wonder
how many just go away and drop the product because of this issue)

The .kmp files you're so against are very simple text files.  You know, those
things unix lovers are always raving about :-) A conversion tool can not do
tn5250 any harm. Ahh, now I see your point. You feel tn5250 would have to
read a whole extra file at run time...?

>From a personal point of view, I just wonder from what authority you speak
when you try and tell me how I (or others) should be using a keyboard? Why
can't I use whizzing cursors and lasoo texts? I don't like emacs, but I don't
go round telling everyone to use vi. I would guess that field-exit is one of
the most important keys on the 5250 keyboard, very much so to data-entry
staff where every single key depression affects their throughput.

Souldn't you be more concerned that the doze version doesn't work, or maybe
you feel tn5250 belongs to *nix? (guess that means there's no mac version
too) It never occured to me until recently (thank's to a couple of post in
this list actually) how much it must cost as/400 sites just to talk to their
boxes. It's probably more obscene that qshell! I think it'll be a long long
time before doze gets replaced in the office, but that's another issue.

No one would mimic ibm's way, it would merely save some poor individual from
having to trawling through months of mailing list archives, looking for the
same old rucurring items. What's wrong with making someone's life easy?


Maybe you've already completed that wonderful howto and all the relevant info
is already available, and I'm just being a prat?




On Monday 27 Aug 2001 22:40 pm, you wrote:
> On Mon, 27 Aug 2001, tonyl wrote:
> > Here's a wish list request:
> >
> > import client access's .kmp (keyboard map) files.
>
> Here is vote to *not* import those files.  tn5250 by and large doesn't run
> on windows machines so why waste time trying to import files created on
> windows machines?  Why should we mimic the IBM way?  I'm sure that there
> are easier ways to handle key-mapping on UNIX machines than trying to
> import Client Access files (even though those files would just tell us how
> the map should be set up).  Just save the map as <insert your favorite
> text file format here - .Xresources format ain't too bad, use XML if you
> want>.
>
> Or don't even worry about keyboard mapping.  Here I've been using tn5250
> since it's initial release (back when I could read all the code and
> understand it in a few hours - and port it to a new arch :) and I don't
> have any problems about how the keys are setup.  Why confuse people by
> trying to make the right control be the enter key?  Just use the key
> labeled 'Enter' as the enter key.  Makes it a lot easier when giving
> support over the phone and you say "Press enter" and you actually mean to
> press the enter key.  Yes we could go fancy with keyboard mapping - but
> should we?
>
> James Rich