- dancer-users - lists.preshweb.co.uk

Dancer::Plugin::Mongo released
by Adam Taylor 17 Oct '10

17 Oct '10

Hi All, Released my first CPAN module and first Dancer::Plugin just now... Dancer::Plugin::Mongo. I guess it will be on CPAN in however long it normally takes.. 24hrs? Otherwise, it's on github - http://github.com/adamtaylor/Dancer-Plugin-Mongo Constructive criticism welcome. Cheers, Adam -- adamjctaylor(a)gmail.com http://www.twitter.com/adamtaylor http://www.adamjctaylor.com

1 0

Re: [Dancer-users] Perl Dancer advent calendar
by Al Newkirk & Associates 13 Oct '10

13 Oct '10

I'd like to tackle the Dancer::Plugin::Authorize article. I've already got some good material for it. -- Al Newkirk

1 0

Dancer::Plugin::FormValidator.
by Natal Ngétal 12 Oct '10

12 Oct '10

Hi, I'm an developper. Perl was my favorite language. I like sa much perl for different reason. I think Dancer was a good choice to develop a web application. Dancer was light, is not close in a model, have a good documentation, good name, and auhtor was cool. I have writing my first plugin I got a choice very easy to begin, I think this a good idea. I'm not a good developper at the moment but I hope that will come with experience. My plugin use Data::FormValidator for validate user input. If error was present I return halt() with a message, else I return 0. You can see my plugin here in github http://github.com/hobbestigrou/Dancer-Plugin-FormValidator , if you have any advice or idea. -- \0/ Hobbestigrou site web: http://erakis.im

4 3

Perl Dancer advent calendar
by Alexis Sukrieh 12 Oct '10

12 Oct '10

Hi fellow dancers, As you may know, we want to publish an Advent Calendar for Perl Dancer. We already gathered a reasonable amount of article ideas[1] and all we need now is to find more and more authors to help us come up with 24 articles before december. Here are the rules to follow if you want to help us in this exciting project (which will be a good marketing action as well as a very good documentation contribution to the whole community). * create a GitHub account if you don't have one * mail the list to notify me or franck you want to contribute to the advent calendat. Mention your GH account and we'll add you to the repository[2] as a contributor (so you'll be able to push there). * Pick up an article in the README and write it in POD (this is mandatory) * When the article is finished, mail the list to request a review. Note that you can also chose to review any existing article, fix typos, ... This is a real community effort! Of course, the more people we have, the better. Looking forward to your help, we can do it! Regards, 1: http://github.com/PerlDancer/advent-calendar-2010/blob/master/README 2: http://github.com/PerlDancer/advent-calendar-2010 -- Alexis Sukrieh

4 4

new Plugin : Dancer::Plugin::Params::Normalization
by damien krotkine 12 Oct '10

12 Oct '10

Hi, As discussed previously, I've implemented a new plugin : Dancer::Plugin::Params::Normalization. This plugins allows to "normalize" parameters names. They can be lowercased, uppercased, ucfirst'ed, or normalized using a given function. The plugin normalizes by default query and body parameters, but can be configured to normalize route parameters too. The plugin can work using 2 policy : 'always', where parameters are automatically normalized, and 'ondemand', where you have to call normalize() to perform the normalization. You can also setup a regexp in the configuration to filter which parameters you want normalized. So, lots of feature, but I think the defaults values make it easy to use at a first glance. It's on github : http://github.com/dams/Dancer-Plugin-Params-Normalization And also on CPAN. Please don't hesitate to comment, hack, propose pull requests, etc... dams

1 0

to_json not JSON-ifying the entire variable
by P Kishor 11 Oct '10

11 Oct '10

I have a data object in JavaScript that I am JSONifying, sending to the server (using jQuery ajax) and storing in a SQLite table. In SQLite, the values look like so (I have prettified it by adding returns and tabs) [ { "a":{"aa":0,"ab":448960000,"ac":"140075520.00"}, "b":1, "c":"foo" } ] I retrieve it via ajax again, and use Dancer's to_json method to send the result back. In Firebug, it shows up as [ { "a":"{\"aa\":0,\"ab\":448960000,\"ac\":\"140075520.00\"}", "b":1, "c":"foo" } ] In other words, to_json seems to stringify all 2nd-level and deeper values. As a result, while the entire value is returned as a JSON object, its internal parts are recognized as strings. That doesn't seem right, no? Its like drinking a cup of coffee, but three sips in finding it to be hot chocolate. I can get around it by reparsing the strings as JSON, but it really shouldn't be so. The data are stored in the SQLite table as a string, so to_json should JSON-ify it all the way through, and send it back as a fully-formed JSON object. -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

2 5

case insensitive param keys
by Mike Schroeder 09 Oct '10

09 Oct '10

When Dancer::Request::_parse_get_params() parses the QUERY_STRING (as I assume the post body), it leaves the key names in whatever case they come in as. I checked some RFCs (http://tools.ietf.org/html/rfc3986#section-6.2.3) to see if there was anything definitive, but not really that I could find. >From a pragmatic perspective, it would be nice to have the keys forced to lowercase by Dancer::Request. If you control every link to your application, then you can do this yourself, but if you have links coming in from external sites, and someone chooses to link to your site as http://www.example.com/?MyPaRAM=Whatever then simple code in Dancer expecting to see params->{myparam} will silently fail. Is this intentional behavior that I need to code around in my app, or something that could be fixed in Dancer::Request? Thanks in advance, Mike. PS: Does anyone know of a good way to search the archives for this list other than using a site: param on google?

8 19

error message not very helpful "status code needs to be an integer greater than or equal to 100"
by P Kishor 09 Oct '10

09 Oct '10

I am getting a lot of status code needs to be an integer greater than or equal to 100 at /usr/local/lib/perl5/site_perl/5.12.1/Plack/Middleware/StackTrace.pm line 27 I can't really point any one reason for the above error. It just seems to be a generic error, and it doesn't help me trace down where what is wrong. Is there anyway I can get better debug info? -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

1 0

error storing session
by P Kishor 08 Oct '10

08 Oct '10

this error is most likely my own doing, so I don't expect solutions, but I am hoping for solutions. I am stumped. If you all recall, not too long ago I created a Dancer::Session>>SQLite plugin. I decided to revisit it, and found it working actually quite well for me (on my laptop). Encouraged, I installed it on my server (also a Mac OS X machine). Installing means I copied the file to /usr/local/lib/perl5/site_perl/5.12.1/Dancer/Session Now, I am stumped as I am getting the following error DBD::SQLite::st execute failed: unable to open database file at /usr/local/lib/perl5/site_perl/5.12.1/Dancer/Session/SQLite.pm line 159. 1. in Plack::Middleware::StackTrace::__ANON__ at /usr/local/lib/perl5/site_perl/5.12.1/Dancer/Session/SQLite.pm line 159 156: VALUES (?, ?) 157: }); 158: } 159: $sth->execute(Storable::freeze($self), $self->id) or die $sth->errstr; 160: $dbh->commit; 161: 162: return $self; This is bizarre. The db exists, is write-able by the web server, and yet, the above execute fails. Can anyone shed any insight into this anomaly? As I said, it works fine on my laptop, but fails on another machine. Yes, the DBI and DBD::SQLite packages are identical and latest on both machines. -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

2 3

Perl Dancer for Python programmers talk slides
by sawyer x 08 Oct '10

08 Oct '10

Hi all. I would like to share a talk I gave at a PyWeb IL meeting (Python web developers) about Perl Dancer. I wrote about it in two recent blog posts[1][2] and you can find the slides here: http://www.slideshare.net/xSawyer/perl-dancer-for-python-programmers or at our new "slides" page of our website: http://perldancer.org/slides *(with the 1.2 release we'll have a new fresh website design)* * *If you've seen the slides since, you should probably see it again since the first conversion wasn't very good and the recent one fixes it[2]. If you've made cool slides for Dancer that you would like to share, please let us know so we can put them on the Dancer website. Au revoir, :) Sawyer. [1] http://blogs.perl.org/users/sawyer_x/2010/10/presenting-perl-dancer-to-pyth… [2] http://blogs.perl.org/users/sawyer_x/2010/10/dancer-for-python-programmers-…

1 0