🚀 go-pugleaf

Sam, did you (ever) upgrade?  I remember their move to GUI, and the implementation was aweful.  It has been a long time, but anything after 4.0 was terrible and not worth it (if I recall correctly.)  SPC/PC 4.0 was the greatest environment.

dvn

-----Original Message-----
From: IBM Mainframe Assembler List
[mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]On Behalf Of Knutson, Sam
Sent: Wednesday, September 07, 2005 2:42 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Assembly coding guidelines


I recently stumbled back through the SPF/PC vendor's page at

 http://www.commandtechnology.com

New SPF/SE 5.0 Available Now

SPF/SourceEdit provides File Management and Editing similar to IBM's
mainframe based ISPF. SPF/SE operates on Windows-95, 98, ME, 2000, NT, and
XP.

Manage large projects with many source files. Edit source code in COBOL,
FORTRAN, PL1, C++, JAVA, DELPHI, PASCAL, XML, HTML, et al. Set up
intelligent editing and colorization for virtually any programming language.
Directly Edit files in ASCII or EBCDIC, in format RECFM=V or RECFM=F, LRECL
up to 64,000.



I queried them about the lack of notification as I last bought v4.0 and was
told they only notified people who upgraded to v4.5 which I didn't see as
worthwhile.

Macros are still C no return of REXX support planned.

It comes in a 3270 and GUI package advertised as separate on the web but I
was told if you want both just ask and I was told it will be provided at no
charge.

$119 to upgrade from any previous version.  I suggested to them that upgrade
price was a little steep.

        Best Regards,

                Sam Knutson, GEICO
                Performance and Availability Management
                mailto:sknutson@geico.com
                (office)  301.986.3574

"Think big, act bold, start simple, grow fast..."




-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Craddock, Chris
Sent: Monday, September 05, 2005 12:53 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Assembly coding guidelines

> 100 characters would work for me. Abandoning the sequence number and
> adding space would even be a good compromise at this point. While I
> love the ISPF sequence numbers at the start of a line the sequence
> numbers at the start of line have been optional for years in xedit.

If you're one of those poor blighted souls who love ISPF, you might be
severely disappointed if you tried editing text files with record lengths
greater than the current screen width. ISPF is pretty user-hateful on this.
(Ask me how I know)

Now admittedly you can define an emulator window with more than 80
characters, so it's not entirely hopeless, but you'll be pretty frustrated
nevertheless. SPF/PC and its cousins are much superior in this respect
because they gracefully handle inserts, nulls etc.

CC
====================
This email/fax message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information.  Any unauthorized
review, use, disclosure or distribution of this email/fax is prohibited.  If
you are not the intended recipient, please destroy all paper and electronic
copies of the original message.