Hi
First thanks for your answer.
At 17:01 16.06.2002, Perrin Harkins wrote:
I have been thinking about a reorganization of the Apache/Perl modules
for
a while, and have come to the conclusion that it would probably be a
good
idea. Please tell me what you think about this proposal.
Sounds fine to me. I would suggest
Also, a module map might be a good thing to create, i.e. an improved
version of this: http://perl.apache.org/src/apache-modlist.html.
Well, because the module list has now moved into the Perl Module List
entirely, we are removing it with the new site.
What I meant was that since you can't
At 18:01 16.06.2002, Perrin Harkins wrote:
Also, a module map might be a good thing to create, i.e. an improved
version of this: http://perl.apache.org/src/apache-modlist.html.
Well, because the module list has now moved into the Perl Module List
entirely, we are removing it with the
Hi,
I am still working on building a framework, design plan for this busy site I
am working on. It is a total revamp so I have the chance to do things right
I have been looking into HTML::Template which is a lot simper than Embed
perl or the template tool kit. I am wondering if anyone has
On Sun, 16 Jun 2002, Eric Frazier wrote:
I have been looking into HTML::Template which is a lot simper than Embed
perl or the template tool kit. I am wondering if anyone has experence with
using both of these with Registry.pm
I do! Back when I worked for Jesse Erlbaum (the author of
soapbox
Grr. Why can't people just write bloody applications with HTML in them
instead of spending so much energy tryuing to find a way to avoid writing
any HTML?
I mean, it's not that hard. Formulate what you want parts to do, make a sort
of vanilla, unformatted output here-doc ior template
At 01:06 PM 6/16/02 -0400, Sam Tregar wrote:
On Sun, 16 Jun 2002, Eric Frazier wrote:
I have been looking into HTML::Template which is a lot simper than Embed
perl or the template tool kit. I am wondering if anyone has experence with
using both of these with Registry.pm
I do! Back when I
Hi,
I think mostly it is about having standards and in a business env making it
so that people who only know part of the picture can still work on the
project as a whole. Sounds like OOP huh? HTML in perl scripts just messes
that whole thing up, like I said before, our fearless leader can mess
Dodger opined on the soapbox:
Grr. Why can't people just write bloody applications with HTML in them
instead of spending so much energy tryuing to find a way to avoid writing
any HTML?
Because I don't want to have to go find a!@#$*^$ Perl programmer every time
the marketing department or a
On Sunday, June 16, 2002, at 07:02 AM, Eric Frazier wrote:
The big points I want to achieve right now, is to make everything I
write
OOP, separate HTML from code as much as possible, and to not make it
impossible to deal with for the people I work with who don't know as
much
perl as I
On Sun, 16 Jun 2002, Jonathan M. Hollin wrote:
I have been thinking about a reorganization of the Apache/Perl modules for
a while, and have come to the conclusion that it would probably be a good
idea. Please tell me what you think about this proposal.
Per Einar, I have cut most your email
12 matches
Mail list logo
