Perrin Harkins wrote:
>
> Drew, if this all sounds like too much trouble for the first draft and you
> already started in HTML, I'd say just finish that up and we'll distill it
> into POD later. (html2pod?)
I have no problems learning something new. I know basic POD, and it
sounds like the tool
On Fri, 4 Aug 2000, Stas Bekman wrote:
> > People are migrating to XML because there are good editors coming onto the
> > market (though sadly none for Linux yet, but I'm getting close to
> > persuading Arbotext to port Adept to Linux...). The editors hide the
> > complexity and you never need to
On Fri, 4 Aug 2000, Matt Sergeant wrote:
> On Fri, 4 Aug 2000, Stas Bekman wrote:
>
> > > > > I hope that you write the doc is POD :)
> > > >
> > > > I suppose I could... I was planning on having a nice checklist of
> > > > features/systems that would be a pain to do in a fixed width font. An
>
On Fri, 4 Aug 2000, Stas Bekman wrote:
> > > > I hope that you write the doc is POD :)
> > >
> > > I suppose I could... I was planning on having a nice checklist of
> > > features/systems that would be a pain to do in a fixed width font. An
> > > HTML table would make my life MUCH easier there.
Gunther Birznieks ([EMAIL PROTECTED]) said something to this effect:
> One book I would highly recommend on CVS is Open Source Development with
> CVS by Karl Franz Fogel. I found it to be not only highly informative but
> an incredibly fun read as well. Each of the semi-dry CVS chapters is
> fo
> > > I hope that you write the doc is POD :)
> >
> > I suppose I could... I was planning on having a nice checklist of
> > features/systems that would be a pain to do in a fixed width font. An
> > HTML table would make my life MUCH easier there. Is there something in
> > POD that makes tables ea
At 08:03 AM 8/4/00 +0100, Matt Sergeant wrote:
>On Thu, 3 Aug 2000, Gunther Birznieks wrote:
>
> > At 05:10 PM 8/3/00 -0700, Perrin Harkins wrote:
> > >On Thu, 3 Aug 2000, Drew Taylor wrote:
> > > > Having recently discovered the joy of CVS, I look forward to it.
> Awfully
> > > > nice to able to
On Thu, 3 Aug 2000, Gunther Birznieks wrote:
> At 05:10 PM 8/3/00 -0700, Perrin Harkins wrote:
> >On Thu, 3 Aug 2000, Drew Taylor wrote:
> > > Having recently discovered the joy of CVS, I look forward to it. Awfully
> > > nice to able to roll back to a previous version - although (knock on
> > >
On 3 Aug 2000, (Randal L. Schwartz) wrote:
> > "Drew" == Drew Taylor <[EMAIL PROTECTED]> writes:
>
> Drew> I suppose I could... I was planning on having a nice checklist of
> Drew> features/systems that would be a pain to do in a fixed width font. An
> Drew> HTML table would make my life MUC
At 05:33 PM 8/3/00 -0700, Randal L. Schwartz wrote:
> > "Drew" == Drew Taylor <[EMAIL PROTECTED]> writes:
>
>Drew> I suppose I could... I was planning on having a nice checklist of
>Drew> features/systems that would be a pain to do in a fixed width font. An
>Drew> HTML table would make my life
At 05:10 PM 8/3/00 -0700, Perrin Harkins wrote:
>On Thu, 3 Aug 2000, Drew Taylor wrote:
> > Having recently discovered the joy of CVS, I look forward to it. Awfully
> > nice to able to roll back to a previous version - although (knock on
> > wood!) I haven't had to use it yet.
>
>I can help if you
> "Drew" == Drew Taylor <[EMAIL PROTECTED]> writes:
Drew> I suppose I could... I was planning on having a nice checklist of
Drew> features/systems that would be a pain to do in a fixed width font. An
Drew> HTML table would make my life MUCH easier there. Is there something in
Drew> POD that m
This
> might end up being kind of big for an in-line, so we could do something
> like "=table data_file.xml" and keep it in a separate file. (Or is it
> better to use "=for html" and put the rest inside that, so that it still
> passes syntax checks for stand
On Thu, 3 Aug 2000, Drew Taylor wrote:
> Having recently discovered the joy of CVS, I look forward to it. Awfully
> nice to able to roll back to a previous version - although (knock on
> wood!) I haven't had to use it yet.
I can help if you get stuck.
> > I hope that you write the doc is POD :)
Stas Bekman wrote:
>
> Sure, no problem. One of the current cvs access holders can commit the
> first release for you, and then you will be able to continue by
> yourself. Obviously getting all the support that you might need on the
> way.
Having recently discovered the joy of CVS, I look forwar
I apologize, I forgot to strip the list's address when sending this.
On Thu, 3 Aug 2000, Stas Bekman wrote:
> [this goes off the list]
...snipped...
_
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http
[this goes off the list]
>
> BTW, you probably don't remember me, but we briefly met at ApacheCon and
Do you have a picture online. I'm sure I'll recall once I see you again!
> I attended your mod_perl classes there (and enjoyed them). :-)
Thanks a lot!
> 501 N. College Street
> Charlotte, NC
> Stas Bekman wrote:
> >
> > On Thu, 3 Aug 2000, Perrin Harkins wrote:
> >
> > > On Thu, 3 Aug 2000, Drew Taylor wrote:
> > > > > Gunther, has anyone found a good home for such a comparison to be
> > > > > hosted? It would be cool if it were at perl.apache.org, or even better
> > > > > at www.p
Stas Bekman wrote:
>
> On Thu, 3 Aug 2000, Perrin Harkins wrote:
>
> > On Thu, 3 Aug 2000, Drew Taylor wrote:
> > > > Gunther, has anyone found a good home for such a comparison to be
> > > > hosted? It would be cool if it were at perl.apache.org, or even better
> > > > at www.perl.com or somet
"Keith G. Murphy" wrote:
> Are there any browsers that do not actually handle the naked '&'
> correctly? I confess that I also missed this, though I do understand
> the reason: the first one's invalid HTML. It just seems to always work.
Think about this:
vs:
Is the © in the first one the H
On Thu, 3 Aug 2000, Perrin Harkins wrote:
> On Thu, 3 Aug 2000, Drew Taylor wrote:
> > > Gunther, has anyone found a good home for such a comparison to be
> > > hosted? It would be cool if it were at perl.apache.org, or even better
> > > at www.perl.com or something (since it's not mod_perl spec
On Thu, 3 Aug 2000, Drew Taylor wrote:
> > Gunther, has anyone found a good home for such a comparison to be
> > hosted? It would be cool if it were at perl.apache.org, or even better
> > at www.perl.com or something (since it's not mod_perl specific). As
> > long as it's easily updatable by its
Ron Pero wrote:
>
[cut]
>
> * Place the templating systems into a spectrum of categories, from simplest
> to most complex/developed.
> It would look approximately like this (not attempting to be complete):
> -Level one, simplest
> * Simple tag/anchor replacement
> * Embedded code
> I think splitting the systems into tiers (simple, average, framework)
> will also help to solve this problem. And of course, the feature
> checklist will be a continually evolving creature.
Absolutely agree. There is no reason to reinvent the wheel. I don't
see why a complete app server syste
Ken Williams wrote:
>
> [EMAIL PROTECTED] (Gunther Birznieks) wrote:
> >I am afraid that while I agree, a check system is really quite useful to
> >me. Some things do need more quantification, but that can be done later.
> >
> >eg lightweight vs heavyweight is subjective. But it can be broken up
on> likes the idea. The Categorical "Congratulations: you wrote a
> Ron> templating system!" web memorial.
>
> Wow, if making suggestions here gets that kind of immediate results,
> let me also suggest I need a girlfriend who is travel-compatible and
> email friendl
Paul J. Lucas writes:
> On Fri, 28 Jul 2000, Malcolm Beattie wrote:
>
> > Assuming the kernel only keeps track of the last fault position in the file,
> > it won't recognise that it's being read linearly (twice :-) and may well not
> > do the async read ahead and drop behind in page cache that it
on> likes the idea. The Categorical "Congratulations: you wrote a
> Ron> templating system!" web memorial.
>
> Wow, if making suggestions here gets that kind of immediate results,
> let me also suggest I need a girlfriend who is travel-compatible and
> email friendl
[EMAIL PROTECTED] (Gunther Birznieks) wrote:
>I am afraid that while I agree, a check system is really quite useful to
>me. Some things do need more quantification, but that can be done later.
>
>eg lightweight vs heavyweight is subjective. But it can be broken up into
>saying something like how
I am afraid that while I agree, a check system is really quite useful to
me. Some things do need more quantification, but that can be done later.
eg lightweight vs heavyweight is subjective. But it can be broken up into
saying something like how much code needs to be loaded at start time (an
i
Matt Sergeant wrote:
>
> On Tue, 1 Aug 2000, Drew Taylor wrote:
>
> > Bill Moseley wrote:
> > >
> > > It seems as if there needs to be a general templating mailing list...
> > >
> > > Here I have a comment about comparing template systems, and then I solicit
> > > advice on which system to use..
>>>>> "Ron" == Ron Pero <[EMAIL PROTECTED]> writes:
Ron> A few days ago I sent this suggestion to Drew Taylor, who is
Ron> preparing a web page comparing the templating systems. He said he
Ron> likes the idea. The Categorical "Congratulations: you
>Maybe we should have a "Congratulations: you wrote a templating
>system!" web memorial. :)
>
>One brief serious note: I think the fact that there are SO MANY is a
>tribute to just how easy it is to process text in Perl. I don't think
>there are 47 templating
Chris,
This sounds precisely like CGI::FastTemplate, which I have used heavily and
like a lot. My other favorite templating system is HTML::Template, but
CGI::FastTemplate is *very* lightweight.
- David
- Original Message -
From: Chris Carline <[EMAIL PROTECTED]>
To: Gunther Bir
Drew Taylor wrote:
>Ken Williams wrote:
>>
>> I suggest having not just a simple checkmark, but a 3-way check. A
>> system either supports a feature, or it doesn't, or it *optionally*
>> supports it (can be switched on and off). This is often very helpful to
>> know, and might let one get a go
Randal Schwartz <[EMAIL PROTECTED]> writes:
>One brief serious note: I think the fact that there are SO MANY is a
>tribute to just how easy it is to process text in Perl. I don't think
>there are 47 templating system for Java. :)
>
Couldn't agree more. Sometimes P
>>>>> "Eric" == Eric Cholet <[EMAIL PROTECTED]> writes:
>> Hi there,
>>
>> I have a pure perl implementation of a simple templating system which is
>> (what I consider to be) relatively lightweight - it copes well in both
>> cgi-b
> Hi there,
>
> I have a pure perl implementation of a simple templating system which is
> (what I consider to be) relatively lightweight - it copes well in both
> cgi-bin and mod_perl environments, at least for me. I've looked at various
> other modules, and do
Hi there,
I have a pure perl implementation of a simple templating system which is
(what I consider to be) relatively lightweight - it copes well in both
cgi-bin and mod_perl environments, at least for me. I've looked at various
other modules, and do believe mine brings an alternative sla
Gunther Birznieks wrote:
> Of course, mod_perl support is crucial for those that want to "scale", but
> normal CGI/Perl support is really a biggie that I haven't seen highlighted
> within the context of this thread.
Most of the popular template modules support CGI use. Almost everything
except A
e if really advanced features aren't used. IE would
rather not have a templating system as large as CGI.pm. Or rather it can be
as large as CGI.pm, but only if the extra code is loaded when advanced
features are accessed -- normal CGI/Perl users should not be penalized.
4) Must have a license tha
>
> > In my mind, almost all my applications seem to fit a system where a my
> > application uses the templates, instead of the templates using my
> > application. In other words, URLs map to the application and not to
> > pages. I assume the likes of TT and HTML::Template fit this, but
> > Embpe
On Tue, 1 Aug 2000, Bill Moseley wrote:
> In additions to a comparison of features, people (including me) might find
> it useful to have a general overview and comparison of the different
> templating _technologies_ and what type of applications work well with each
> and why.
I was planning to
Yup, there wasn't nearly enough time at the conference. I don't think I'll
be able to make ApacheCon Europe :( but I'm still interested in working
together.
Jon
On Thu, 27 Jul 2000, Matt Sergeant wrote:
>
>Jonathan and I spoke briefly at the conference about working together on a
>combined effor
Matt Sergeant wrote:
>
> On Tue, 1 Aug 2000, Drew Taylor wrote:
>
> > Bill Moseley wrote:
> > >
> > > It seems as if there needs to be a general templating mailing list...
> > >
> > > Here I have a comment about comparing template systems, and then I solicit
> > > advice on which system to use..
>
> Look at the history of this list: it often gets very bursty and the quiet
> again. I think setting up a perl-template mailing list would be initially
> heavily trafficed, but be pretty much dead in a few weeks (or days even).
>
I agree to that
Gerald
-
On Tue, 1 Aug 2000, Drew Taylor wrote:
> Bill Moseley wrote:
> >
> > It seems as if there needs to be a general templating mailing list...
> >
> > Here I have a comment about comparing template systems, and then I solicit
> > advice on which system to use...
> >
>
> Bill,
>
> After all the r
"Erich L. Markert" wrote:
>
> Drew Taylor wrote:
> >
> > Bill Moseley wrote:
> > >
> > After all the response the thread generated, I wonder if perhaps we
> > (meaning the people who have control over those things :-) really
> > _should_ setup another list.
> >
>
> I could see the efficacy of a
Drew Taylor wrote:
>
> Bill Moseley wrote:
> >
> After all the response the thread generated, I wonder if perhaps we
> (meaning the people who have control over those things :-) really
> _should_ setup another list.
>
I could see the efficacy of a template developers site for those people
invol
Bill Moseley wrote:
>
> It seems as if there needs to be a general templating mailing list...
>
> Here I have a comment about comparing template systems, and then I solicit
> advice on which system to use...
>
Bill,
After all the response the thread generated, I wonder if perhaps we
(meaning
It seems as if there needs to be a general templating mailing list...
Here I have a comment about comparing template systems, and then I solicit
advice on which system to use...
The only reason I'm using my own templating system (besides the requirement
that everyone writes one) is beca
brian moseley wrote:
>
> On Fri, 28 Jul 2000, Drew Taylor wrote:
>
> > Anything that would make the above scenario easier would
> > get a thorough look in future templating system
> > decisions. In short, I'm looking for a good, FLEXIBLE
> > application
Perrin Harkins wrote:
>
> On Fri, 28 Jul 2000, Drew Taylor wrote:
> > Andy Wardley wrote:
> > >
> > > And the REALLY, REALLY smart ones (i.e. TT2) can write the Perl code to
> > > disk for persistance of compiled templates. That way, the templates
> > > never need to be re-compiled (i.e. from TT
On Fri, 28 Jul 2000, Drew Taylor wrote:
> Anything that would make the above scenario easier would
> get a thorough look in future templating system
> decisions. In short, I'm looking for a good, FLEXIBLE
> application framework. I'm tired of writing it all
> myse
Hi *,
thank you all for your comments on the plain-ampersand-in-URL-problem.
I received many useful hints regarding this subject, so I thought I might
as well sum them up for those who have missed this thread.
In short:
If you have URLs in your HTML with more than one query-string arg
(a
On Sun, 30 Jul 2000, Andy Wardley wrote:
> Yes, the great thing about Embperl and other embedded Perl solutions is
> that the "parsing" phase only really requires the Perl code to be
> extracted from the text.
And you know this is faster than parsing the HTML ... how,
exactly?
> Embperl's parser have used from the startup only C code, maybe that's the
> reason why the time this takes (compared to the rest of the request) never
> was an issue for me...
Yes, the great thing about Embperl and other embedded Perl solutions is
that the "parsing" phase only really requires t
> >
> > Is there any way for Embperl to get access to other apache
> > modules (like the C++ versions of the xerces xml parser
> > or xalan xslt processor)? It would be nice to be able
> > to reuse the same code in or out of embperl.
>
> Only by writing XS (or swig) code. Please feel free to do
On Fri, 28 Jul 2000, Drew Taylor wrote:
> Andy Wardley wrote:
> >
> > And the REALLY, REALLY smart ones (i.e. TT2) can write the Perl code to
> > disk for persistance of compiled templates. That way, the templates
> > never need to be re-compiled (i.e. from TT syntax to Perl code) unless
> > you
On Fri, 28 Jul 2000, Drew Taylor wrote:
> After all this discussion, what would benefit me most in choosing my
> next template system would be a concise central repository of the
> features & benefits for the major template systems (TT, Apache::ASP,
> Embperl, Mason, & HTML::Template come to mind
On Sat, 29 Jul 2000, Leslie Mikesell wrote:
> According to Gerald Richter:
> > >
> > > The TT parser uses Perl regexen and an LALR state machine.
> >
> > Embperl's parser have used from the startup only C code, maybe that's the
> > reason why the time this takes (compared to the rest of the requ
According to Gerald Richter:
> >
> > The TT parser uses Perl regexen and an LALR state machine.
>
> Embperl's parser have used from the startup only C code, maybe that's the
> reason why the time this takes (compared to the rest of the request) never
> was an issue for me...
Is there any way for
>
> The TT parser uses Perl regexen and an LALR state machine.
Embperl's parser have used from the startup only C code, maybe that's the
reason why the time this takes (compared to the rest of the request) never
was an issue for me...
Gerald
On Thu, 27 Jul 2000, Paul J. Lucas wrote:
> On Thu, 27 Jul 2000, Matt Sergeant wrote:
>
> > > > http://www.best.com/~pjl/software/html_tree/
>
> > Aside from the GPL, it does looks nice.
>
> What's wrong with the GPL? It's open-source and free of cost.
> What more do you w
> But you have to recompile the Perl code, which normaly takes more time, then
> compiling the template to the Perl code. I don't think that this will gain
> very much speed. (Maybe in case of TT this is more important, because it has
> to first translate his own language to Perl code, while other
s just a simple templater.
That's fine. What I am objecting to is the (mis-)use of the term
"Templating system". A template is a passive sheet of metal or
plastic with holes in it. It does not include levers and gears and
motors.
--
Frank Cringle, [EMAIL PROTECTED]
voice: (+49 2304) 467101; fax: 943357
On Fri, 28 Jul 2000, Malcolm Beattie wrote:
> Assuming the kernel only keeps track of the last fault position in the file,
> it won't recognise that it's being read linearly (twice :-) and may well not
> do the async read ahead and drop behind in page cache that it would do
> otherwise. Once agai
[EMAIL PROTECTED] (Frank D. Cringle) wrote:
>Drew Taylor <[EMAIL PROTECTED]> writes:
>> Ken Williams wrote:
>> >
>> > I suggest having not just a simple checkmark, but a 3-way check. A
>> > system either supports a feature, or it doesn't, or it *optionally*
>> > supports it (can be switched on a
Drew Taylor <[EMAIL PROTECTED]> writes:
> Ken Williams wrote:
> >
> > I suggest having not just a simple checkmark, but a 3-way check. A
> > system either supports a feature, or it doesn't, or it *optionally*
> > supports it (can be switched on and off). This is often very helpful to
> > know,
Yes, a cookie-munging facility would be nice
-Original Message-
From: Drew Taylor
To: David Hodgkinson
Cc: [EMAIL PROTECTED]
Sent: 7/28/2000 10:25 AM
Subject: Re: Templating System
David Hodgkinson wrote:
>
> Drew Taylor <[EMAIL PROTECTED]> writes:
>
> > While
Matt Sergeant wrote:
>
> This is getting too complex. Just do a couple of paragraphs on each, and
> let everyone bang it out to a bit more than that. I guarantee that once
> one template system designer says "Mine does X", the others will chime in
> and say "Well mine can do X too, and optionally
On Fri, 28 Jul 2000, brian d foy wrote:
> On Fri, 28 Jul 2000, Michael Hanisch wrote:
> > Personally I would attribute the described problem to a bug in IE4 - even
> > if it parses the URI for entities, it shouldn't find a "§" since the
>
> Alan Flavell has an excellent article on this problem,
On Fri, 28 Jul 2000, Michael Hanisch wrote:
> I really believe my thoughts outlined in my original post are correct -
> but right now I am starting to worry...
> Personally I would attribute the described problem to a bug in IE4 - even
> if it parses the URI for entities, it shouldn't find a "§"
Paul J. Lucas writes:
> > This is the quote from "Philip and Alex..." that I was talking about
> > earlier. I don't know if its relevant or not:
> >
> > They replied "NaviServer uses memory-mapped file I/O on single-processor
> > machines but automatically configures itself to use operating syste
On Fri, 28 Jul 2000, Drew Taylor wrote:
> Ken Williams wrote:
> >
> > I suggest having not just a simple checkmark, but a 3-way check. A
> > system either supports a feature, or it doesn't, or it *optionally*
> > supports it (can be switched on and off). This is often very helpful to
> > know,
Ken Williams wrote:
>
> I suggest having not just a simple checkmark, but a 3-way check. A
> system either supports a feature, or it doesn't, or it *optionally*
> supports it (can be switched on and off). This is often very helpful to
> know, and might let one get a good sense of the difference
On Fri, 28 Jul 2000, Paul J. Lucas wrote:
> > This is the quote from "Philip and Alex..." that I was talking about
> > earlier. I don't know if its relevant or not:
> >
> > They replied "NaviServer uses memory-mapped file I/O on single-processor
> > machines but automatically configures itself t
> This is the quote from "Philip and Alex..." that I was talking about
> earlier. I don't know if its relevant or not:
>
> They replied "NaviServer uses memory-mapped file I/O on single-processor
> machines but automatically configures itself to use operating system read on
> multi-CPU machines s
[EMAIL PROTECTED] (Drew Taylor) wrote:
>Gerald Richter wrote:
>>
>> >
>> > Vivek had an excellent suggestion in private email: put together a list
>> > of features and let the developers check off the options their system
>> > supports. My biggest question is who comes up with the feature list in
I might as well pipe up.
I very much enjoy using HTML::Mason.
And people keep calling it inline perl, while it is really a hybrid
inline/templating solution (i.e. <%init> blocks keeps much of the perl
code separate, but in the same file.
It would, however, be nice to combine the best features o
Gerald Richter wrote:
>
> >
> > Vivek had an excellent suggestion in private email: put together a list
> > of features and let the developers check off the options their system
> > supports. My biggest question is who comes up with the feature list in
> > the first place?
> >
> I would suggest i
>
> Vivek had an excellent suggestion in private email: put together a list
> of features and let the developers check off the options their system
> supports. My biggest question is who comes up with the feature list in
> the first place?
>
I would suggest it the other way round. Put together wha
Gerald Richter wrote:
>
> > As for summarizing, I have some pretty good info already: a private
> > email from a user of embperl, Andy's post of TT, and Joshua pointed me
> > to Apache::ASP's website. I'll probably do some serious reading this
> > weekend and (hopefully) begin to sketch out the c
> As for summarizing, I have some pretty good info already: a private
> email from a user of embperl, Andy's post of TT, and Joshua pointed me
> to Apache::ASP's website. I'll probably do some serious reading this
> weekend and (hopefully) begin to sketch out the comparison. And yes,
> help is alw
>
> And the REALLY, REALLY smart ones (i.e. TT2) can write the Perl code to
> disk for persistance of compiled templates. That way, the templates
> never need to be re-compiled (i.e. from TT syntax to Perl code) unless
> you change them. They can simply be loaded via Perl's require().
>
But you
On 7/28/00 12:54 PM, Mark Doyle wrote:
> We deliberately chose to use URL's with a series of '/' delimited fields
> rather then using '? ... &' style URL's precisely because most people
> don't know they have to escape the ampersands and we didn't want to risk
> people's links breaking in the
Okay, I think there is still some confusion here as to what I am shooting
for. Ideally, I would like a system where the static parts of the page are
cached. I have recieved several mails suggesting that items such as the
header/footer can be turned into compiled print() statements as part of
the
At 13:28 28/07/2000 +0200, Michael Hanisch wrote:
>To be honest, I have always used plain ampersands in URLs embedded in my
>pages, and thus far I have never encountered any problems.
>But maybe I've just been lucky... ;-)
Forget about all those mindboggling HTML questions ! Use XHTML, there &
is
> From: Michael Hanisch <[EMAIL PROTECTED]>
> Date: 2000-07-28 06:48:14 -0400
> Are you really positive about this?
Randal is 100% correct.
> AFAIK (and I just looked it up in the HTML 3.2 spec :-) the tag is
> defined as follows:
>
> (quoted from http://www.w3.org/TR/REC-html32#sgmldecl)
> S
If there was only one way to do it, it wouldn't be perl. :)
On Thu, 27 Jul 2000, Erich L. Markert wrote:
> OK, I'm nearing the end of one project so I'm able to take a look at new
> solutions so one question comes to mind. What does the template toolkit
> offer above and beyond HTML::Embperl
Perrin,
I am about to embark on the same journey you describe below. My initial
thoughts were just to highlight features/difference/drawbacks for each
of the major templating systems. Have you done any work to date on this
project? I would like to begin reseaching each of the systems this
weekend
or fields incorrectly entered or missing. I currently do it my
> grabbing form input, do some basic checking for each group of info, save
> it to the DB, and then display either for form again with the
> missing/error fields highlighted or show a response.
>
> Anything that would make t
"Randal L. Schwartz" wrote:
>
> > "Jacob" == Jacob Davies <[EMAIL PROTECTED]> writes:
>
> Jacob> Now as to ampersands used to separate form fields, like:
>
> Jacob>
>
> Jacob> do you mean that it should be:
>
> Jacob>
>
> Jacob> instead? That second one looks better now that I look
On Fri, 28 Jul 2000, Paul J. Lucas wrote:
> On Fri, 28 Jul 2000, Kenneth Lee wrote:
>
> > it would be good for the user to choose between mmap or normal i/o at
> > compile time. i'll try HTML::Tree anyway in the meantime.
>
> It's not that simple. Using mmap(2) greatly affects how one
>
Andy Wardley wrote:
>
> And the REALLY, REALLY smart ones (i.e. TT2) can write the Perl code to
> disk for persistance of compiled templates. That way, the templates
> never need to be re-compiled (i.e. from TT syntax to Perl code) unless
> you change them. They can simply be loaded via Perl's
Simon,
You aren't the only one who was pleasantly surprised to come back to a
mailbox overflowing with messages on a topic near & dear to my heart.
:-)
As for summarizing, I have some pretty good info already: a private
email from a user of embperl, Andy's post of TT, and Joshua pointed me
to Ap
On Fri, 28 Jul 2000, Kenneth Lee wrote:
> it would be good for the user to choose between mmap or normal i/o at
> compile time. i'll try HTML::Tree anyway in the meantime.
It's not that simple. Using mmap(2) greatly affects how one
writes code: it's not a drop-in replacement fo
On Jul 27, 10:55am, David Hodgkinson wrote:
> Smart templaters cache templates and results. The REALLY smart ones
> compile the templates into perl code and hold them as a reference to
> an anonymous sub.
And the REALLY, REALLY smart ones (i.e. TT2) can write the Perl code to
disk for persistance
ew Taylor <[EMAIL PROTECTED]> Date 14:54:16 28 July
2000
To: modperl <[EMAIL PROTECTED]>
cc:(bcc: Simon Wilcox/BASE/WilliamsLea)
Fax to:
Subject: Feature sets [was Re: Templating System]
After all this discussion, what would benefit me most in choosing my
it would be good for the user to choose between mmap or normal i/o at
compile time. i'll try HTML::Tree anyway in the meantime.
Matt Sergeant wrote:
>
> On Thu, 27 Jul 2000, Paul J. Lucas wrote:
>
> > On Thu, 27 Jul 2000, Gerald Richter wrote:
> >
> > > To keep it fast Embperl is written in C
101 - 200 of 313 matches
Mail list logo
