|
I'm trying to force myself to use wdsc, but
> it's a really slowdown in production when > you only know how to enter and compile the > code, and don't know how to test it. How is using WDSC for editing and compiling slower than using PDM for you?
I always end up back at the green screen
> for most of the real work.Me too. There's no reasonable way to use a GUI to test a 5250 green screen application. And I don't mean that the IBMers can't figure it out, I mean how can you do 5250 emulation without emulating a 5250? :-)
At the moment, I'm not getting any
> of the joy you all are professing.I myself don't get a big thrill out of the colour coding and I've only started to use the outline view. The big thing for me is being able to see lots of lines of code on the screen, the ability to use regexes for searching, reasonable tab stops and bookmarks.
I personally got much better with a GUI editor when I stopped trying to make Brief act like SEU with a GUI accent. The lesson being that in order to use LPEX, I have to edit the LPEX way. I have been using GUI editors since the early 90s, so my experience is a bit different from some, but I find it noticeably slower to edit with SEU than LPEX just because of the time it takes to move the cursor around the code.
--buck
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.
midrange.com
