+1 for a DCF clone. All of our system's documentation is in BookMaster, for 
which we have (had?) a perpetual license. But we don't have Script/VS anymore, 
so we can't change the documentation. I mean, obviously we can /change/ the 
source, but we can't /format/ it for PDF.

BookMaster is just macros, so it would be platform independent. The key is the 
Script/VS engine.


And before you link to it, no IBM's BookMaster to HTML converter has too many 
bugs to be useful. I've fixed a few but the rest are daunting.

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Seymour J Metz
Sent: Friday, October 25, 2024 7:14 AM
To: [email protected]
Subject: Re: SPFSource Edit 365 profile paths

Alas, CTC dropped Rexx support with SPF/SE, and before that they were very lax 
about ISPF compatibility. That's why I opted for Tritus SPF, which is still my 
preferred text editor. TSPF had excellent ISPF compatibility not just for edit 
macros but also for dialogs.

I just wish that somebody would be willing to take my money for an upgrade. I 
would also love to be abled to buy DCF, BookMaster and BookManager clones for 
Linux. Of course, open source would be better, but I'd cheerfully pay if that 
were the only option.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר



________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
Schmitt, Michael <[email protected]>
Sent: Thursday, October 24, 2024 11:30 AM
To: [email protected]
Subject: SPFSource Edit 365 profile paths

Caution: This email did not originate from George Mason’s mail system. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.


This is just FYI, for current and prospective users of the now free SPF/SE 365 
< https://github.com/michaelknigge/spf-editor/blob/main/README-v365.md >...

Here's what's documented in the above linked Read Me:

The SPF/SE 365 Build 3454 installer gives a choice of two installations:

A. Install for all users: SPFSE365 will be installed in C:\Program Files (x86). 
The user's profile will be in C:\ProgramData\SPF SourceEdit 365.
B. Install for current users: SPFSE365 and the user's profile will be in 
folders in the user's AppData path.

In either case, some customized profile members (i.e. not part of the retail 
distribution) are included in the user's profile folder.

But what if you want the program to be installed in C:\Program Files (x86), but 
have a per-user profile? You know, like normal applications.


Here's what is NOT documented, and I've found in testing:

SPF/SE 365 supports three levels of profile folders:

 - Default profile: installed in a \Profiles subfolder where the executable is 
installed
 - All Users profile: installed in C:\ProgramData
 - User profile: installed in a per-user folder

The build 3454 installer doesn't work this way.

Instead, it is installing as described above, and then setting the SPFGE365RW 
environment variable to point to where the user's profile folder is. Note: This 
is not a typo; "GE" is for Graphic Edition.

Here's the crucial point: When the SPFGE365RW environment variable is used, you 
don't get the 3 level profile structure. You only get two levels: the default 
profile and the user profile.


So...

If you want to install the program in Program Files, but have a per-user 
profile:

1. Install for All Users. Then, BEFORE FIRST LAUNCH:
2. Copy C:\ProgramData\SPF-Options to the desired user folder, e.g. 
C:\Users\<user>\AppData\Roaming\SPF-SE 365\
3. Set a user environment variable SPFGE365RW to point to the user profile path


If you want the three level profile structure, which keeps the user's profile 
modifications separate from the customized profile files delivered with the 
application, then the All Users and User profile folders MUST be named exactly:

  All Users: C:\ProgramData\SPF-Options\Graphic
  User:      C:\Users\<user>\SPF-Options\Graphic

1. Install for All Users. Then, BEFORE FIRST LAUNCH:
2. Create a subfolder "Graphic" in C:\ProgramData\SPF-Options and move all the 
profile files to it. That is, the profile folder should be 
C:\ProgramData\SPF-Options\Graphic, not C:\ProgramData\SPF-Options.
3. Delete the SPFGE365RW system environment variable

On first launch, SPF/SE 365 will create the user profile folder in 
C:\Users\<user>\SPF-Options\Graphic.


___________________________________________________
Michael Schmitt | DXC Apps Development | MassMutual
(737) 910-8248 | [email protected]

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to