Greetings.
On Mon, 19 Aug 2002, Pierre Vaudrey wrote:
with the following starnge error (The Title is displayed but not the
vignette.gif file)
[Mon Aug 19 07:22:24 2002] [error] Missing right curly or
square bracket
at /Library/WebServer/Documents/perl/vignette.gif line 1,
at
Le mardi 20 août 2002, à 09:32 AM, Alessandro Forghieri a écrit :
Greetings.
On Mon, 19 Aug 2002, Pierre Vaudrey wrote:
with the following starnge error (The Title is displayed but not the
vignette.gif file)
[Mon Aug 19 07:22:24 2002] [error] Missing right curly or
square bracket
at
On Mon, 19 Aug 2002, Pierre Vaudrey wrote:
with the following starnge error (The Title is displayed but not the
vignette.gif file)
[Mon Aug 19 07:22:24 2002] [error] Missing right curly or square bracket
at /Library/WebServer/Documents/perl/vignette.gif line 1, at end of line
syntax error
Pierre Vaudrey wrote:
I'm trying to run the following HTML::Template simple example :
[...]
Could anybody help me to fix it ?
Pierre, you are asking an HTML::Template question at the wrong forum,
seems that this is the place where you want to ask this instead:
On Sep 4, 2:46pm, Sam Tregar wrote:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
That isn't really much better, in my opinion. It's still too much of a
departure from the HTML around it.
That's the point. It's not HTML markup so you should make
On Mon, 4 Sep 2000, Marc D. Spencer wrote:
o There are actually 3 groups involved, and separation of function
as much as possible allows the three groups to work independently on
a project without requiring concurrent editing of the same file.
- HTML coders
-
Hi all,
On Tue, 5 Sep 2000, Matt Sergeant wrote:
Thats the whole point of these discussions...
I'm not sure that there's any point to these discussions.
Do you think this one could go off-List now?
73,
Ged.
[EMAIL PROTECTED] (Marc D. Spencer) writes:
I have to chime in a little (also noting that we have drifted a bit
off the original topic...)
While working for a large company as the Chief Architect for the web
group I was faced with the same need to investigate template options
- within
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl apps.
Vivek Khera wrote:
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl apps.
I'm also finding it useful. There have been many
On Tue, 05 Sep 2000 10:39:37 -0400, Drew Taylor wrote:
I'm also finding it useful. There have been many useful ideas/concepts
thrown about that I intend to use in the template comparison.
Seconded. Lots of useful stuff in this thread, and has been giving me a lot of
information about other
Hi all,
On Tue, 5 Sep 2000, Drew Taylor wrote:
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl apps.
I'm also finding it
"G.W. Haywood" wrote:
Hi all,
On Tue, 5 Sep 2000, Drew Taylor wrote:
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl
There are several points that we should consider before we can succesfully
compare different templating systems. Performance, Ease of use, Code
maintainability, Learning curve and the "Programming eficiency" (lines of
code you have to write to have your job done) are some (good?) examples.
A
To which HTML::Template responds: "Sure you know Perl, but does the HTML
designer you're working with?" HTML::Template has a simple, HTML-esque
syntax for its template files that is aimed at HTML designers.
I still think that this:
? foreach $name (@names) { ?
Name: ?=$name? P
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
I agree that one shouldn't put lots of code inside of a template, but
variables and loops are better expressed in Perl than in a "little
crippled language".
You and I are programmers and we agree. However once you move to a larger
"Nelson" == Nelson Correa de Toledo Ferraz [EMAIL PROTECTED] writes:
Nelson And the first one has two major advantages: 1) requires less
Nelson code in the Perl modules and 2) allows designers to know how
Nelson Perl looks like.
Is this a codeword for "share our pain"? :)
Perhaps any HTML
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4 Sep 2000, Randal L. Schwartz wrote:
Nelson And the first one has two major advantages: 1) requires less
Nelson code in the Perl modules and 2) allows designers to know how
Nelson Perl looks like.
Is this a codeword for "share our pain"?
On Mon, 4 Sep 2000, Billy Donahue wrote:
I've been working with JSPs lately, and I'd use something like:
jsp:useBean name="someIterator" type="java.util.Iterator"
dadadada:iterator iterator="%= someIterator %"
table
tr
thName/th
thAddress/th
/tr
At 11:26 AM 9/4/00 -0300, Nelson Correa de Toledo Ferraz wrote:
I agree that one shouldn't put lots of code inside of a template, but
variables and loops are better expressed in Perl than in a "little
crippled language".
Your example makes perfect sense to me. But that's why I'm in "Tech" and
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
I still think that this:
? foreach $name (@names) { ?
Name: ?=$name? P
Job: ?=$job{$name}? P
? } ?
Is cleaner (well, as much as perl can be :-)) than this:
TMPL_LOOP NAME=EMPLOYEE_INFO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Sep 2000, Matt Sergeant wrote:
That said, I am a mod_perl novice, and I don't know if there's anything
equivalent or better than this in the mod_perl world.
Well to stick the AxKit oar in, yes, of course there's something better...
On Mon, 4 Sep 2000, Matt Sergeant wrote:
You and I are programmers and we agree. However once you
move to a larger shop where you'll find non-programmers
editing templates, the HTML-ish loop looks more sensible
than an entirely new language, unfortunately.
i used to believe this argument. i
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
You and I are programmers and we agree. However once you
move to a larger shop where you'll find non-programmers
editing templates, the HTML-ish loop looks more sensible
than an entirely new language,
On Mon, 4 Sep 2000, Billy Donahue wrote:
Which is close enough to HTML that the HTML people
should understand it. You never really have to "break
character" while writing presentation pages. I prefer
the custom tags approach to the embedded code approach..
See, in Java you're better off
On Mon, 4 Sep 2000, Matt Sergeant wrote:
In AxKit your developers design custom "taglibs" that
allow you to design your own tags however you want them
to appear. There's a built in taglib for SQL, which
allows you to produce XML from a DBI database, but
writing taglibs is relatively easy.
brian moseley [EMAIL PROTECTED] writes:
i used to believe this argument. i was all up on the xslt
bandwagon. and then i took the question to our html dept.
and they unanimously preferred perl.
Looking for better paid jobs, I'd guess... ;-)
--
Dave Hodgkinson,
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
In AxKit your developers design custom "taglibs" that
allow you to design your own tags however you want them
to appear. There's a built in taglib for SQL, which
allows you to produce XML from a DBI
On Mon, 4 Sep 2000, Matt Sergeant wrote:
Unusual bunch :-)
don't think so. xslt is overly verbose and complicated, and
its model is the inverse of the standard html page. whereas
a nice little mason page with some simple embedded perl
looks enough like what everybody's used to, to not be big,
On Mon, 4 Sep 2000, brian moseley wrote:
ah. well anyway, it's ubiquitous, and everybody's got
it. everybody that counts, anyway, imo.
mr bungle redundant .. redundant .. redundant
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
I still think that this:
? foreach $name (@names) { ?
Name: ?=$name? P
Job: ?=$job{$name}? P
? } ?
Is cleaner (well, as much as perl can be :-)) than this:
TMPL_LOOP NAME=EMPLOYEE_INFO
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
Unusual bunch :-)
don't think so. xslt is overly verbose and complicated, and
its model is the inverse of the standard html page. whereas
a nice little mason page with some simple embedded perl
looks
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
is cleaner still: *pure* HTML (no fake elements)
That's because you're a Perl programmer. The template syntax wasn't
designed for your tastes. It was designed for the HTML designers you will
eventually have to work with - wether while you're actually on the project
or when it moves into maintainance and needs design changes.
That's a
On Mon, 4 Sep 2000, Perrin Harkins wrote:
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Sep 2000, Paul J. Lucas wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
That's because you're a Perl programmer. The template syntax wasn't
designed for your tastes. It was designed for the HTML designers you will
eventually have to work with - wether while you're actually on the project
or when it
On Mon, 4 Sep 2000, Matt Sergeant wrote:
I was questioning whether or not your HTML people found
Perl easier than some taglib scheme like HTML::Template,
or whether you meant they found it easier than XSLT.
ah yes. xslt vs mason, specifically.
again. With XSLT you can markup your article
On Mon, 4 Sep 2000, Perrin Harkins wrote:
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
To a HTML monkey, all those curly brackets, question
marks and dollars are magical. All you've done is reduce
some keystrokes. Looks fine to a perl programmer, looks
like a modem init string to a
On Mon, 4 Sep 2000, Billy Donahue wrote:
Great, as long as there's no loops or anything but straight up text
replacement... I don't like this approach at all!
What I showed *was* a loop; read my other follow-up.
What if you need to actually USE the `class' attribute of your HTML
"Paul J. Lucas" wrote:
What about conditionals and loops though?
Wouldn't they break the "preview" ability?
No: for loops, you just get one iteration; for conditionals, you
get the result as if the condition were true.
Thanks for the explanation. I can still think of
On Mon, 4 Sep 2000, Matt Sergeant wrote:
b) We all meet different people. The people I've worked
with, even people proficient in Javascript, flip their
lid when they get forced to look at things like $_ and
regexps when they know of easier systems out there. And
I know what SF is like -
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
b) We all meet different people. The people I've worked
with, even people proficient in Javascript, flip their
lid when they get forced to look at things like $_ and
regexps when they know of easier
I was trying to stay out of this one, but...
brian moseley wrote:
% for my $thing (sort @list) {
a href="% $thing-{url} %"b% $thing-{name} %/b/a
% }
[...]
there are no sophisticated or mysterious constructs in those
examples...
Just two kinds of data structures, hash de-referencing
On Mon, 4 Sep 2000, Perrin Harkins wrote:
I can still think of situtations in applications I've worked on where there
were mutually excusive chunks of HTML that would have looked funny with this
approach, but it gets you about 95% of the way towards a previewing system
for free. Cool.
On Mon, 4 Sep 2000, Perrin Harkins wrote:
Embedded perl is absolutely the best answer sometimes, but don't
underestmate the value of turning your example into this:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
That isn't really much better, in my
On Mon, 4 Sep 2000, Matt Sergeant wrote:
Thats not how SQL taglibs work in things like AxKit and
Cocoon. The taglib generates a data structure, which
gets processed in the next stage of the pipeline (this
is more efficient than it sounds, but the efficiency is
hidden from the user).
oh
On Mon, 4 Sep 2000, Perrin Harkins wrote:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
what's the value? you have to write a parser and then
interpret the instructions. that's what eval() is for! and
your syntax is no prettier or easier to understand
According to Steve Manes:
At 11:26 AM 9/4/00 -0300, Nelson Correa de Toledo Ferraz wrote:
I agree that one shouldn't put lots of code inside of a template, but
variables and loops are better expressed in Perl than in a "little
crippled language".
Your example makes perfect sense to me.
I love this perennial thrash. My 2 cents: don't underestimate the value
of having mobility in the separation of "engineer" and "production" ('HTML
Monkey', as it's been previously referred too, ee ee). Mason's ability to
have components that are all Perl, all FooML or a mix in the two allows
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
is cleaner still: *pure* HTML (no fake elements) that
Nah
You do not want the Perl to look like the HTML at all so the HTML
designers aren't confused.
Also - why put so much perl into the page at all?
[- use mymodule.pm -]
Sam Tregar wrote:
On Mon, 4 Sep 2000, Perrin Harkins wrote:
Embedded perl is absolutely the best answer
On Mon, 4 Sep 2000, Eric L. Brine wrote:
Great idea, but just one note; ':' is not legal in CSS class names. In
fact, underscores are not even allowed in CSS class names!
So? They aren't CSS class names. The are in fact legal
class names according to the HTML spec.
I have to chime in a little (also noting that we have drifted a bit
off the original topic...)
While working for a large company as the Chief Architect for the web
group I was faced with the same need to investigate template options
- within the discussion of Build or Buy. And yes, JSP (and
ELB Great idea, but just one note; ':' is not legal in CSS class names.
ELB In fact, underscores are not even allowed in CSS class names!
PL So? They aren't CSS class names.
In the preview mode, they are treated as such, so in effect they are.
Therefore, the document claims does not conform
On Mon, 4 Sep 2000, Eric L. Brine wrote:
ELB Great idea, but just one note; ':' is not legal in CSS class names.
ELB In fact, underscores are not even allowed in CSS class names!
PL So? They aren't CSS class names.
In the preview mode, they are treated as such, so in effect they are.
brian moseley wrote:
On Mon, 4 Sep 2000, Perrin Harkins wrote:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
what's the value?
It's easier for some people to understand and write without help from an
engineer.
you have to write a parser and
On Mon, 28 Aug 2000, Nelson Correa de Toledo Ferraz wrote:
"This approach has two problems: First, their little language is
crippled. If you need to do something the author hasn't thought of, you
lose. Second: Who wants to learn another language? You already know
Perl, so why not use
Nelson Correa de Toledo Ferraz wrote:
Hi Drew,
I'm the one who volunteered, and then I went on vacation for a 2 weeks.
I have decided I will have a bare minimum draft done within a week. And
then, as Matt suggested, people can just send
suggestions/corrections/additions and the
Matt Sergeant wrote:
On Tue, 15 Aug 2000, Gunther Birznieks wrote:
Is there an ETA on when this will be out?
I know everyone is busy, but I just figured I would ask. There have been
hundreds of template messages generated in the last weeks on this topic,
and then it seems to have
Matt Sergeant wrote:
If nobody is working on it, I suggest just getting 1 or 2 paragraph
synopsis from template authors about thier product. Just compile those
together and then let it evolve as people see other people's paragraphs
and think "Hey I should have mentioned X too...".
I would
Hi Drew,
I'm the one who volunteered, and then I went on vacation for a 2 weeks.
I have decided I will have a bare minimum draft done within a week. And
then, as Matt suggested, people can just send
suggestions/corrections/additions and the document will grow. When I
have a draft, I'll post
On Tue, 15 Aug 2000, Gunther Birznieks wrote:
Is there an ETA on when this will be out?
I know everyone is busy, but I just figured I would ask. There have been
hundreds of template messages generated in the last weeks on this topic,
and then it seems to have gone a bit quiet (as usual).
Whilst we're on the subject of templates, would anyone care to comment
on how they fit with content-negotiated documents? I'm looking at
a document for multiple language using Apache
MultiViews. (index.html.es, index.html.jp etc). Does this even work
with SSI or Apache::SSI?
TIA,
Dave
--
On Tue, 15 Aug 2000, Gunther Birznieks wrote:
Was someone (or somepersons) committed to doing this or is the project
seeking volunteers or both?
Drew Taylor [EMAIL PROTECTED] was working on the first cut, and I was
planning to add some things on to that. As with The Guide, I'm sure that
all
66 matches
Mail list logo
