Re^2: How do you use Template Toolkit with Dancer2?

Using Template::Toolkit, create a template like this:

<select name="[% name %]" >
[%- FOR option IN options %]
<option [% FOREACH attr IN option.attributes.keys %][% attr %]="[% opt
+ion.attributes.$attr %]" [% END -%]
[%- IF option.default %]selected="selected" [% END -%]
value="[% option.value %]">[% option.label %]</option>
[%- END %]
</select>
[download]

In Dancer2 code, just call it with

return template 'menu',
    {name    => 'menu_name',
     options => [
         {value => 'eenie',  label => 'your first choice', attributes 
+=> {class => 'first choice'}},
         {value => 'meenie', label => 'your second choice', default =>
+ 1},
         {value => 'minie',  label => 'your third choice',  default =>
+ 1}],
     }
[download]

Update: Accept any attributes, not just class (not sure I'd recommend it).

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

Comment on Re^2: How do you use Template Toolkit with Dancer2? Select or Download Code

Replies are listed 'Best First'.
Re^3: How do you use Template Toolkit with Dancer2? by PiotrS (Novice) on Apr 27, 2022 at 13:54 UTC
Thank you for your suggestion. When I tried to encapsulate this code in a subroutine, and call it in another subroutine, Dancer2 seems to automatically use the main template located in the layout directory as a wrapper to this snippet, as well at to the entire page that generated an undesired visual effect. Ideally, it should be possible to write a simple subroutine that returns a menu, that, in turn can be invoked in some other subroutine that generates an arbitrary form: `sub dropdown_menu { # should generate only an HTML snippet of a menu #my ..arguments..; return template 'form_menu.tt', { ...argument hash... }; } . . . get '/' => sub { # generates the actual form that is used as [% conten +t %] in the layout/main.tt template template 'some_form.tt', { menu1 => dropdown_menu(...parameters1...), menu2 => dropdown_menu(...parameters2...), radio1 => radio_group(...parameters3...), . . } }` [download] Does that make sense, or am I accidentally breaking some Dancer2 paradigm? I apologize if this question is trivial.	[reply] [d/l]
Re^4: How do you use Template Toolkit with Dancer2? by choroba (Cardinal) on Apr 27, 2022 at 18:36 UTC
Yes, you're breaking the Model - View - Controller paradigm. You can include the dropdown menu template from other templates, sending only the data from the code (i.e. no "dropdown_menu" in the code). `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l]
Re^5: How do you use Template Toolkit with Dancer2? by PiotrS (Novice) on Apr 29, 2022 at 01:07 UTC
Thank you for your answer. If a menu template can be included in a "parent" template, how would one go about including two or more menus in the "parent" template, where the difference is only the menu's name and the data-set. Wouldn't that introduce ambiguity to the assignment of variables within the menu template?	[reply]
Re^6: How do you use Template Toolkit with Dancer2? by choroba (Cardinal) on Apr 29, 2022 at 07:30 UTC


Welcome to the Monastery
	PerlMonks