FNSnap
Posted: Mon Sep 12, 2011 12:30 pm
THis is a new topic started by Gordon's comment in Client Server thread regarding FNSnap.
My intention in building FNSnap is to create a library that is generically useful to anyone using Business Rules language. At the beginning of the effort I did include some functions that were specific to my software, however, I have been working on removing those pieces from the library. There are still a few "oboslete" functions that are in the library that are specific to me. I will remove those. They have to do with look-up routines for my spceific file structure. I have moved these to separate libraries, but not deleted the code in all cases from FNSNAP
In addition, there are a few, also obsolete functions that relate to my screen painter. Those are specific to a certain screen width, but are obsolete and should be removed. Those functios have been moved to my NEWSCRN.dll utility that a few people have been using.
The single ENV$ dependency that exists throughout the FNSNAP library is the ENV$("PD") variable. I use this consistenltly to point to the parent directory of "Vol002", the directory in which I keep FNSNAP.dll. In most cases the ENV$("PD") variable is exactly the same as the ":" starting point for BR, but not always, depending on how the program is entered. ENV$("PD") can be set in WBCONFIG.SYS or in a menu program or in some other way. Once set the FNSNAP libraries will use its location to find Vol002 an the FNSNAP.dll library within it.
There are some functions that call outside executables, such as David Blankenship's BRREGISTER2.exe registry reader. FNSNAP expects to find these in the ENV$("PD")&"vol002" directory. (ENV$("PD") ends with a backslash as in "C:\WB\").
If anyone finds an instance where I have limited the usefulness of FNSNAP by including parameters that do not work with your particular set up please shoot me an email and I will do my best to adjust FNSNAP so that it is more generic.
In addition to the ENV$ dependency noted above I do use a file that I call "TT" to load certain systemwide variables into programs using a "PROC *:TT" or "PROC "&env$("PD")&"TT". That file is loacted in the BRG directory of the FTP site. I also use a few fonts that I tend to prefer. Those are also loaded with a PROC statement, so in both cses you can change the files being PROCed to fit your own set up and not have them changed each tiome I issue an updated FNSNAP.
I always load FNSNAP as a resident library just before loading and running my menu. That way the rather large library does not need to take up time to load in every chain. It can be a significant time saver.
I hope you all find the functions useful and would welcome any constructive comments.
FNGeorge
My intention in building FNSnap is to create a library that is generically useful to anyone using Business Rules language. At the beginning of the effort I did include some functions that were specific to my software, however, I have been working on removing those pieces from the library. There are still a few "oboslete" functions that are in the library that are specific to me. I will remove those. They have to do with look-up routines for my spceific file structure. I have moved these to separate libraries, but not deleted the code in all cases from FNSNAP
In addition, there are a few, also obsolete functions that relate to my screen painter. Those are specific to a certain screen width, but are obsolete and should be removed. Those functios have been moved to my NEWSCRN.dll utility that a few people have been using.
The single ENV$ dependency that exists throughout the FNSNAP library is the ENV$("PD") variable. I use this consistenltly to point to the parent directory of "Vol002", the directory in which I keep FNSNAP.dll. In most cases the ENV$("PD") variable is exactly the same as the ":" starting point for BR, but not always, depending on how the program is entered. ENV$("PD") can be set in WBCONFIG.SYS or in a menu program or in some other way. Once set the FNSNAP libraries will use its location to find Vol002 an the FNSNAP.dll library within it.
There are some functions that call outside executables, such as David Blankenship's BRREGISTER2.exe registry reader. FNSNAP expects to find these in the ENV$("PD")&"vol002" directory. (ENV$("PD") ends with a backslash as in "C:\WB\").
If anyone finds an instance where I have limited the usefulness of FNSNAP by including parameters that do not work with your particular set up please shoot me an email and I will do my best to adjust FNSNAP so that it is more generic.
In addition to the ENV$ dependency noted above I do use a file that I call "TT" to load certain systemwide variables into programs using a "PROC *:TT" or "PROC "&env$("PD")&"TT". That file is loacted in the BRG directory of the FTP site. I also use a few fonts that I tend to prefer. Those are also loaded with a PROC statement, so in both cses you can change the files being PROCed to fit your own set up and not have them changed each tiome I issue an updated FNSNAP.
I always load FNSNAP as a resident library just before loading and running my menu. That way the rather large library does not need to take up time to load in every chain. It can be a significant time saver.
I hope you all find the functions useful and would welcome any constructive comments.
FNGeorge