Is this of any interest? HTML::Menu::Select
Use the menu() subroutine if you want to have a template like this:
<form>
<TMPL_VAR select_menu>
<input type="submit">
</form>
Use the options() subroutine if you want to have a template like this:
<form>
<select>
<TMPL_VAR select_menu>
</select>
<input type="submit">
</form>
You could use it something like this:
use CGI 'header';
use HTML::Template;
use HTML::Menu::Select 'menu';
my $tmpl = HTML::Template->new( ... );
my $select = menu(
name => 'response',
values => ['yes', 'no'],
default => 'yes',]
onChange => 'alert(this.value);',
);
$tmpl->param( select_menu => $select );
print header();
print $tmpl->output;
See the docs for more info. The arguments are mostly compatable with CGI.pm's
popup_menu routine (though I've just realised I haven't yet documented
how they differ (todo!).
I've also upgraded HTML::Menu::DateTime to use this,
so it can optionally generate the HTML rather than data structures.
Still on the to-do list though, is JS validation
-
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.