|
That's a great list of features--more than I could think of off the top of my head. I love it myself and have been promoting it actively at work for over six months. So far I've only gotten two people to try it and made one convert. The other found the lack of field exit support to be more than enough reason not to use it. One more thing--you can see more than 40 lines of source on a 19 inch monitor. > -----Original Message----- > From: Paul Tuohy [mailto:tuohyp@attglobal.net] > Sent: Thursday, October 10, 2002 1:14 PM > To: midrange-l@midrange.com > Subject: Re: Tabs in SEU > > > <snip> > > "Tyler, Matt" wrote: > > > It's just that, in my experiences, CODE/400 has not offered > anything to > > actually enhance the coding experience. You can code > off-line but you still > > have to get on-line to verify the program and get cross-reference. > > <end-snip> > Hmmmmmmmmmm. Gotta disagree with you on this Matt. > > What comes to mind immediately..... > > - Color coding lines. > - Tab sensitive in free form. > - Full online help for RPG (don't know about help for Cobol etc.). > - Wizards for D specs and subprocedures in RPG and a couple > of wizards for Java > and the ability to write any wizards I want. > - See more then 70 odd characters without damaging my eyes on > a 25*132 screen. > - See more the 16/18 lines of code at a time. > - Edit more then one member without having to have a 5250 > session per edit. > - Navigator to give me a chart of a program. Double click on > the subroutine box > and you are positioned at the line of code in the source. > - Verify a program. Yes, you have to be on line, but only the > first time you > verify. After that the verify can be from the cache on your > PC - average verify > time for a 600 line program on my PC is under two seconds. I > do most of my > coding off-line and I verify all the time. > > A quick comparison between detecting a simple mis-spelling of > a field name > using Code and SEU. > > Code: Click on verify, double click on 7030 message no and > you are at the > error. > SEU: F3, 14 Enter, Get message the job ended abnormally, 2 > Enter, F15, 2 > Enter, Move cursor to SEU command line on bottom half of > screen, B Enter, Page > Up twice, F 7030 Enter, F16, F16, move cursor to line no on > top half of screen, > Type line no in error and Enter. > > <snip> > > > I think everyone should try CODE/400 for them selves, but I > just want to warn > > others that it is not the fix for all dislikes with SEU. Both have > > limitations that need to be resolved and we all suspect > that IBM will no > > longer update SEU with new features, beyond the exit points. > > <end snip> > > No argument here. Code/400 is not perfect (few if any windows > based products > are) but I have found it to be streaks ahead of SEU. It does > take some getting > used to because old habits are hard to break - we know how to > do things > instinctively in SEU but we have to think about it when we > are using Code/400 > ergo SEU suits me better - just have to give it a bit of time. > > As for the bug discussion - "One man's bug is another man's feature" > > Regards > > Paul Tuohy > > > _______________________________________________ NOTICE: All e-mail sent to or from this e-mail address will be received or otherwise recorded by The Sharper Image corporate e-mail system and is subject to archival, monitoring, review by and/or disclosure to Sharper Image security and other management. This message is intended only for the use of the addressee and may contain information that is privileged and confidential. The contents of this message may contain personal views which are not the views of The Sharper Image. If you are not the intended recipient, dissemination of this communication is prohibited.
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.