Hello Stefan,
Historians believe that Wednesday, June 4, 2003 at 21:57 GMT -0400 was
when, Stefan Tanurkov [ST] typed the following:
The Beta looks very good, just a few questions
ST> [*] Completely rewritten template subsystem with possibility to add
ST> macros from plug-ins.
What is the format for these plug-ins? Does any unknown macro in a
template get routed to the installed plug-ins?
ST> [*] New syntax for macros: it is now possible to use brackets instead
ST> of ="..." (in some cases it is now required - see below).
This doesn't always work. For the %Cookie macro, with brackets, the
macro assumes the base directory is the directory that the program was
opened in. With the old style, the absolute path is used.
For example:
%Cookie="C:\Temp\Oneliners" works as expected.
%Cookie(C:\Temp\Oneliners) gives error:
Cannot open file "C":\Temp\OneLiners)
The bracket system also fails on complex %SetPattRegexp macros. It
looks like TB gets confused as to what part is the macro and what part
is the string if it is legal to have brackets as part of the string.
That's not really surprising, but should probably be documented.
Note: %Cookie("C:\Temp\Oneliners") also works as expected.
ST> [+] %VARnnn="..." (equal to %_nnn="...") macros to set variables, use
ST> %VARnnn (or %_nnn) to insert variable value. Variable name can
ST> contain alphabet characters, digits and "_"
This is really nice. Please document the fact that the variables can
be passed back and forth between parent and child templates. It
appears that you've made the scope of the variables global. This is
fine, but should be documented.
Also, how long is the variable defined? Is it as long as the macro
engine is running, or is it defined as long as the message is being
edited? In other words, can I run one template which defines a
variable, then manually run a second template which accesses that
variable?
ST> [+] %SETHEADER("RFC Name","Value") macro to set a message header to
ST> the Value, use %ADDHEADER("RFC Name","Value") to add value to a
ST> header, use %HEADER("RFC Name") to retrieve value of a header
ST> (%OHEADER("..") retrieves header from the original message)
Here it looks like strings should be enclosed in quotes when using the
new bracket system. However, this doesn't work for the %QInclude
macro. There, the QT name *must* not be enclosed in quotes. For
%OHeader, it seems the quotes are optional. So is the necessity of
the quotes with the brackets somewhat arbitrary, or is there a method
to the madness?
How flexible is the quote character in the new bracketed syntax? With
the old syntax, we could replace the double quote character with any
character. Is that also true of the new syntax?
Also, how would one mix strings and macros with the new bracket
system?
--
Thanks for writing,
Januk Aggarwal
Using The Bat! 1.63 Beta/8 under Windows 98 4.10 Build 2222 A
________________________________________________________
Current beta is 1.63b7 | "Using TBBETA" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
