|
Hi Jon and Steve,
You speak from experience, so I won't put the figure of 40% into question then.
However personally I keep mixed feelings about still adding SEU
functionality. Working towards a "normalized" editor would be
preferable imho.
Kind regards,
-Arco
Op za 9 feb. 2019 om 19:22 schreef Jon Paris <jon.paris@xxxxxxxxxxxxxx>:
But the capability has been _added_ Aco. None of the existing "modern iDE" behaviour has been removed. So what's the problem?
And speaking as someone who trains SEUers in RDi believe me it does help to have this as a more familiar option.
Interestingly, my partner Susan has started using the "SEU view" recent despite many many years of code400/WDSC/RDP/RDi because it just makes it easier to do some things.
Op ma 11 feb. 2019 om 01:20 schreef Steve Ferrell via WDSCI-L
<wdsci-l@xxxxxxxxxxxxxxxxxx>:
Hi Arco,
Yes the latest figure I saw was about 40% still on SEU or PDM. The PDM enhancements to RDi aren't about making RDi like PDM, but to give those users a bridge. November 2017 the class I was in was nearly 58% of users at a presentation on RPGILE with Susan. The entire room was using RPGLE for 20+ years, but nearly 2/3 of the classroom wasn't using RDi. Biggest reason from surveys? No time to learn a new UI.
Many of our trainers report that even new developers like using PDM commands to cc, b, a, and dd. Once they find them they like keeping their hands on the keyboard instead of reaching for the mouse.
That's the real goal of the PDM perspective in the future. No needing to reach for you mouse, and much simpler interfaces for these commands. Sure sometimes a user may need all of the parameters on a command, but 90% of time they don't. So it's about giving a simple interface to all users, without taking away from RDi users.
Steve Ferrell
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.