Is this okay?2) This is what I have for the sub _perform_searchHere is what I have so far:1) in the simple form what should I put for action=?Hi John,I couple questions about your sample above:
<form action="index.tt">
Query:<br>
<input type="text" name="query" value="Mickey">
<br><br>
<input type="submit" value="Submit">
</form>
sub _perform_search(
my $fake_search_results = 'Comcast loves net neutrality";
return $fake_search_results;
)2015-08-07 15:15 GMT-05:00 John Stoffel <john@stoffel.org>:
Andrew,
I think you really need to back up and start from scratch
again. Unfortunately I've got family around and can't spend the time
to help directly, but what I would do is:
1. start a new dancer project.
2. build a new template for the index page with a <form ....>
... </form> in it with just a single text entry and a submit button.
Simple stuff. Make sure the text post has a name of 'query'.
3. You need two routes in your lib/Module.pm file:
package Module;
use Dancer ':syntax';
use Dancer::Plugin::DBIC;
our $VERSION = '0.1';
get '/' => sub {
template 'index', {
title => "The Index",
};
};
get '/search' => sub {
my $query = params->{query} || "";
my $regexp = $query;
$regexp =~ s/\?|\*/\.\*/g;
my $tobold = $query;
$tobold =~ s/\?|\*//g;
my @results = ();
my $limit = 50;
if (length $query) {
@results = _perform_search($regexp,$limit);
}
}
And of course a subroutine called _perform_search() to do the actual
work.
Once you have that working, try using the POST method, and adding in
the:
post '/search2' => sub {
}
routines. Then you *should* be able ot handle it.
I'd also look more closely at the Dancer Advent calendar stuff as
well. The advantage of GET calls is that you can more easily wrap
them into a div and return results, etc.
But honestly I'm an old dog also learning new tricks... :-)
John
_______________________________________________
dancer-users mailing list
dancer-users@dancer.pm
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users