Ken,
As mentioned before, I'm interested in moving the status/error messages
that are currently displayed *before* the html template to *inside* the html
template. I've figured out how to do this, and want to make sure this is
something that you are willing to integrate into qmailadmin before taking
the time to do it (there's a good bit to do).
Here's what will happen:
There's a new "case" in template.c that looks like this:
case 'S':
fprintf(actout,"%s", StatusMessage);
break;
Also I've added:
to qmailadminx.h:
extern char StatusMessage[MAX_BIG_BUFF];
to qmailadmin.c:
char StatusMessage[MAX_BIG_BUFF];
Each html template will have a new "hook" named "##S" that will be just
below the <body> tag.
Lastly, and most time consuming, will be changing how the "StatusMessage" is
displayed. For example: In addusernow(), I've changed this:
if ( fixup_local_name(Newu) ) {
fprintf(actout, "<h2>%s %s</h2>\n", get_html_text("148"), Newu);
adduser();
vclose();
exit(0);
}
To this:
if ( fixup_local_name(Newu) ) {
sprintf (StatusMessage, "<h2>%s %s</h2>\n", get_html_text("148"), Newu);
adduser();
vclose();
exit(0);
}
And voila! You now get this html:
<html>
<HEAD>
<Title>QmailAdmin</Title>
</HEAD>
<BODY bgcolor=#FFFFFF>
<h2>Invalid Email Address </h2>
<CENTER>
--SNIP--
*Instead of (old way)*
<h2>Invalid Email Address </h2>
<html>
<HEAD>
<Title>QmailAdmin</Title>
</HEAD>
<BODY bgcolor=#FFFFFF>
<CENTER>
--SNIP--
It'll take some time to convert everything over, but I believe this will
improve template flexibility a lot.
Do you, or anyone else have any thoughts for or against this? Any ideas on
doing this in a better way?
Cheers,
Bill Shupp
