[Info-vax] PC/VT Keyboarrd Mapping

[Jan-Erik Soderholm]

Den 2016-06-25 kl. 18:59, skrev David Froble:
> Jan-Erik Soderholm wrote:
>> Den 2016-06-25 kl. 14:20, skrev Stephen Hoffman:
>>> On 2016-06-25 01:26:25 +0000, David Froble said:
>>>
>>>> Why is it that whatever you use is great ... and whatever I use should
>>>> die?
>>>
>>> There are fewer keyboards with keypads, too.
>>
>> It's not what I'm seeing. Many new "professional" laptops has
>> larger screens today, and it seems as the manfacturers just as
>> well put in a real keyboard with numeric kaypad also.
>>
>> And besides, even if you have an laptop, most professionals will
>> hook up an external keyboard and screen anyway.
>>
>>> Unfortunately what you're using — the keypad-based application...
>>
>> You've got to keep applications apart from the editing.
>> I use EDT to edit our web based "GUI" applications.
>>
>>> and keypad-based editors — is dying out...
>>
>> EDT isn't "dying". Or, it is dying at the same pace as VMS is.
>>
>>> OpenVMS apps either need to forget about the VMS-layout LK and/or provide
>>> an alternative to the keypad...
>>
>> The keypad works just OK on any standard PC keyboard. With a few small
>> differences that should be easy to learn for any IT professional.
>>
>> Or are you now talking about the end-user applications? Yes, they should
>> not be depending on VT-style kayboards and keys, and they will probably
>> mostly be based on web interfaces, so it is a non-issue. I do not see
>> a huge volume of newly written VT-based applications today.
>>
>> But that is something completely different then me using EDT.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> What he wrote ....
>

OK. The difference might be that you are talkning about yourself.
I try to look at the VMS world at large, as far as I know it.

I think the "market" I'm looking at is slightly larger then
the one you are talking about.

If one look at the VMS markets today (banking, large companies
logistics back-office), that is not VT-based.

And again, we should not mix up the end-users environment
with what we as programmers might prefer or use.