Everything you said about Petal applies to Seamstress. However, the
advantage of Seamstress is that you don't need to learn a
mini-language.
So let's take the same content:
Welcome back <b tal:content="user/name">Sample Username</b>,
you last logged in <i tal:content="user/last_login">Sat 23rd Aug</i>
And when you look at this in dreamweaver or a browser you'll see
Welcome back Sample Username, you last logged in Sat 23rd Aug
And assuming
$h = {
user => {
name => "Fergal Daly"
last_login => "Feb 22nd"
}
}
The processed output will be
Welcome back Fergal Daly, you last logged in Feb 22nd
Now for the big difference
Of course TAL handles loops and conditionals etc.
Seamstress does not. Perl has loops and conditionals and sees no need
for their re-invention.
The thing that takes the most getting used to is that it's a little
verbose. Unfortunately this is a necessary side effect of being
truly compatible with XML/HTML.
I agree with you here, but I personally could have it no other way
either. Here is how seamstress would template the same thing:
require html::welcome_form;
my $tree = html::welcome_form->new;
my $user_name = $tree->look_down('tal:content' => 'user/name');
$user_name->replace_content($hash->{user}{name});
my $last_login = $tree->look_down('tal:content' => 'user/last_login);
$last_login->replace_content($hash->{user}{last_login});
or with a loop
for my $content (qw(name last_login)) {
$tree->look_down('tal:content' => $content)
->replace_content($hash->{user}{$content});
}
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.