It may not be very portable either -- a fair number of us aren't running
Apache.
-----Original Message-----
From: David Harris
Sent: Thursday, August 10, 2000 10:59 AM
To: L.C.; [EMAIL PROTECTED]
Subject: RE: Modular Client Code Proposal
L.C. wrote:
> You may want to take a look at Embedded Perl (Embperl), it does EXACTLY what
> you are asking and much more, it is a very good tool for building interfaces
> in perl. http://perl.apache.org/embperl/index.html
>
> You can then include separate header files too, although you realize that you
> will eventually end up with XML or style sheets to get a consistent look all
> around without changing every FONT tag in the page :-)
Embperl allows you to embed your Perl IN the template, which is the opposite
of
the code-template-separation that I was proposing with Template-Toolkit.
With Template-Toolkit you can't chuck perl code in your template. (Well, you
can by turning an option, but it is not encouraged.) It forces you to put all
the code over HERE and the template over THERE. With Embperl you can toss
them
all together.
Now some people write a Perl module for their interface and make simple calls
to that from Embperl but that's not the real strict separation that OpenSRS
needs.
David Harris
President, DRH Internet Inc.
[EMAIL PROTECTED]
http://www.drh.net/
