This Function Call Has become a litle advanced. At least in that its time to Explain how it works. In short - it takes parameters that tell it how to build a HTML page from templates. It does this and returns the compiled HTML.
p_saArea: is the HTMLRIPPER template filename without the file name extension. If nothing is passed then the filename specified in grJASConfig.saDefaultPage is used (This file MUST Exist even if it is not actually used for SECTION ONLY calls Explained below) First this file is searched for in the same directory the JEGAS CGI THIN CLIENT is launched from. Then it looks in the configured JAS HTML directory for it. If an AREA file (Default or otherwise) cannot be located and loaded - an error is returned to the user. (Case Sensitive. Lowercase .html presumed)
p_saPage: This is the HTML file that has the SECTION you wish to load. It first search for this file in the directory the JEGAS CGI THIN CLIENT was launched in. If it is not there, it looks in the configured JAS HTML directory. If the file cannot be loaded, an error is generated. (Case Sensitive. Lowercase .html presumed) (Note: IF ANYTHING AT ALL IS PASSED in the p_saCustomSection parameter, then this PARAMETER is IGNORED!)
p_saSection: This is the NAME of the SECTION you want to RIP out of the p_saPage template. Sections are discerned from HTML comments that look like: <!–SECTION SECTIONNAME BEGIN–> <!–SECTION SECTIONNAME END–>
The above "SECTIONAME" is where you name your section. Do not use spaces, USE ALL UPPERCASE. The parameter you pass to look for the the section does not need to be in uppercase. This is done for you.
If the SECTION cannont be found in the html template file you specified in p_saPage, then the whole p_saPage data is sent. This is usually undesired, so make your HTML templates carefully.
(Note: IF ANYTHING AT ALL IS PASSED in the p_saCustomSection parameter, then this PARAMETER is IGNORED!)
p_bSectionOnly: If this parameter is passed as true, this function only returns the HTML in between the SECTION TAGS explained above or the p_saCustomSection value.
(optional) p_saCustomSection: This parameter allows you to send HTML and have it inserted into the AREA template. Because this overrides the p_saPage and p_saSection parameters, and allows you to pass your own CUSTOM SECTION into an AREA (htmlripper) template, you can get silly results by setting the p_bSectionOnly flag to true. Simply put, if you do that (not likely you should) this function will simply return your passed custom section. NOTE: Caller parameter added so you can track who called the function when debugging. Optimizations could include compiler directives to electively compile without the extra debugging code - then again - its helpful when you're LIVE too!