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

What about a "use Dancer :config"?
by Cymon 08 Sep '13

08 Sep '13

Hi all, I was a little puzzled when I saw the "Use Dancer :syntax" disappear in the 0.007 release. I thought that a less powerful Dancer inclusion was needed as the "Use Dancer" create an App in every package is used. Thinking about it I realized that probably it's a matter of "code discipline" (tell me if I'm wrong). The right way to do things is not importing "a part" of Dancer environment, but passing the $dsl object when needed, so I accepted that. Even so, I think that there's a case when a "light" dancer import is needed and it is when you need to use some configuration you have in the config.yml that should be the master configuration file for everything in your project (in my idea). So I was wondering if it could be useful to add a "Use Dancer :config" way to import Dancer just to make the config keyword accessible, without creating an App. What do you think about this? -- Simone "Cymon" Faré http://perlishscrewdriver.blogspot.com

3 4

Using Dancer2 as a website framework
by Greg Kempe 07 Sep '13

07 Sep '13

Hi, I'm hoping for the community's input on whether Dancer is an appropriate framework for our project. We're building a website that wraps functionality exposed by an existing Perl EPP library. Perl has great EPP support and we don't want to re-implement that library in another language. In the medium term, the website will need to offer a fairly rich user experience that calls out to other databases and services beyond this one library. We're exploring two options: 1. use Dancer to build the entire website 2. use Dancer to power a thin REST API around the library and use another framework (eg. in Python) to build the rich website experience. Our requirements include: * move quickly, use the right tool for the job (ie. favour re-using components over building everything from scratch) * modern website tooling, such as SASS for CSS, good HTML form support, model validation * well documented and mature software * relatively easy for other devs to work on the project later I'm deliberately trying to avoid a language flame war. Rather, I'm evaluating based on the size and maturity of the User Experience/UI section of the Perl community. Dancer seems well placed for API servers, but the web dev communities seem to be focused around Ruby, Python, Node etc. which is making me lean toward option (2) above. Is that a reasonable evaluation? What do you all think? Thanks, Greg

9 17

New Dancer 2 release: 0.09
by sawyer x 04 Sep '13

04 Sep '13

Hi everyone! We've just cut a new release of Dancer 2. I thought you might like to know about the recent changes done. Mickey Nasriachi continued his work on the core. This is the second release he has appeared in. This time he cleaned up the DSL and made more things immutable (a major target for us), and sped up route compilation, fixed some issues and so on. Do continue on your rampage! Russell Jenkins is determined to close as many open holes as we can find. He has fixed a "forward" problem, cleaned up some of the serializers' behavior and most importantly corrected inaccurate PSGI handling in one edge case that was really bugging me. Thank you, Russell! Ahmed Zawawi joined Dancer history by making his first contribution (congratulations!) by cleaning up a bit in the documentation that confused people and suggesting a proper way of handling reloading while developing. Another new comer in Dancer history is Alex Beamish who also cleaned up a bit of documentation. It's an often-overlooked aspect of projects but it's nothing short of crucial for beginners. And one more new comer is Andrew Solomon who had helped with documentation as well as being quite visible in Github, trying to help us sort out things, and fleshing out possible issues. Welcome Ahmed, Alex and Andrew! If you check the Changes file, you will probably see Alberto Simões and myself. Alberto fixed the autopages (along with the help of Russell) and a small fix in log levels with config files. The autopage fix was extremely important for me, and I'm personally thrilled to have a team that is so in-tuned with working on things that actually trouble people directly. I've been quite busy myself as well, but I managed to work on removing the Dancer ModuleLoader with Class::Load, with a hand from Alberto. This means loading is faster and more correct. I've removed the not-quite-implemented "load_app" keyword and the documented-but-non-existent "load" keyword. With Dancer 2 you just do "use App". It seems we have also successfully phased out the "devel" branch. I've been working on some bigger things in Dancer, but they will take time to ripen. I want to thank all the contributors for their help. You have made Dancer 2 that much better and we appreciate it. A special thanks goes to Alberto for the constant probing and poking to make sure PRs get attention, fixes are done, and releases are made. I also want to give a big shout out to Alexis Sukrieh (sukria), who helped out behind the scenes with throwing ideas around, discussing implementation, providing insight and support. You might not see him much, but he is alive and kicking! Also, he will be at the upcoming Portuguese Perl Workshop. If you're there and I'm not, give him a hug for me. :) Keep in touch! If you have any feedback, please do let us know: mailing list, Github, personal emails, it's all there for you to use. See you next release, Sawyer X, Dancer core team.

2 1

New Dancer incoming - Hannover.pm
by BURNERSK 04 Sep '13

04 Sep '13

Hi all. Dancer is cool so we of Hannover.pm decided to use Dancer for our Perl Mongers homepage. Build a very tiny Dancer CMS around it. Feel free to add it to http://www.perldancer.org/dancefloor :D http://hannover.pm/ -- Cheers, Sören BURNERSK Hannover.pm

5 4

Dancer 1 v1.3118 is on its way to CPAN
by Yanick Champoux 01 Sep '13

01 Sep '13

Good morning dancers, It is my pleasure to announce that I've just cried havoc and slipped out the Dancer of war. Release 1.3118 is on its way to CPAN, and it carries a fair amount of goodies (see below). As usual, a big thank you and a heap of props to everyone who reported bugs, submitted patches, offered advice, displayed patience and silently passed the bottle of rotgut when it was needed. You are the ones keeping the dance floor alive. Joy, DJ `/anick 1.3118 01.09.2013 [ ENHANCEMENTS ] * GH #946: new 'require_environment' setting. (Jesse van Herk) * GH #952: don't set defaults for Template subclasses for Dancer::Template::TemplateToolkit. (Rick Myers) * GH #945: add function 'template_or_serialize' to Dancer::Serializer::Mutable. (Yanick Champoux) [ BUG FIXES ] * GH #655: clarify logger error message. (Yanick Champoux, reported by Gabor Szabo) * GH #951: fix quoting of TemplateToolkit start_tag/stop_tag. (Rick Myers) * GH #940: carry over the session when we forward(). (Yanick Champoux, reported by sciurius) * GH #954: don't die on autoflush for older perls. (Yanick Champoux, reported by metateck and David Golden) * GH #950: Dancer::Test functions now populate REQUEST_URI. (Yanick Champoux, reported by Sören Kornetzki) [ DOCUMENTATION ] * GH #942: simpilify the Apache deployment docs for cgi/fcgi. (bug report by Scott Penrose) [ MISC ] * GH #949: fixes a few errors in the serializer testsuite. (Franck Cuny)

2 1

Long-term contract telecommuting role using Dancer, Moose, DBIC etc
by David Precious 30 Aug '13

30 Aug '13

Hi all, Anyone interested in a long-term contract position using Dancer, Moose, DBIx::Class and other modern Perl goodness to work on large backend systems in a domain registration and hosting environment, please feel free to drop me a mail off-list. Full-time (40 hours a week) preferred, although part-time may be considered. You would be working within our geographically spread team, with permanent members in the UK, and contractors in the Ukraine, Russia, India and elsewhere. May also be considering a permanent UK position soon, if I can get the appropriate budget secured, but that's not for sure yet; until I can secure any more budget, I'm unlikely to be able to get approval for an appropriate salary for a UK-based employee at the current time. Cheers Dave P -- David Precious ("bigpresh") <davidp(a)preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github

1 0

Phasing out "devel" branch on Dancer 2
by sawyer x 22 Aug '13

22 Aug '13

Hi everyone! Following a small comment in the last release announcement, we're working on phasing out the "devel" branch (akin to "develop" branch elsewhere) on the Dancer 2 Git repo. The purpose of this change is to make it easier to contribute to Dancer 2, and to make it easier for us to manage it and release it. We're keeping the branch for now, but switched the main branch to "master". If you're starting a new pull request, basing your changes on "master" would be appreciated. If not, we'll work it out, don't worry about it. If you've submitted work rebased on the "devel" branch, we will create a new branch on "master" and cherry-pick your work on that, and then merge it back to master. We will not remove the branch for at least a few months to allow forks to become synced with the change. Either way, you should never fear to submit changes. Our policy remains the same: *any contribution via any channel is accepted and encouraged*. Patches, email notes, IRC messages, commits against "master", "devel" or any other branch. We're open to any contribution form. Have a great week, Sawyer.

1 0

New Dancer 2 release: 0.08
by sawyer x 22 Aug '13

22 Aug '13

Hey, we have just released a new version of Dancer 2: 0.08. While it didn't carry everything we had wanted (one specific change was left for 0.09), we decided it is more important not to delay features and fixes. We can also do another release next week, right? This release saw at least 16 closed tickets. Not a bad record. There were also several important changes that were not described in tickets and were resolved as well. The release also saw me struggling with a Dist::Zilla plugin, resulting in no date put on the changes file entry. This will be fixed in the next version. Hopefully I will win that round. :) The following people deserve thanks for this release (not ordered in any way): Russell Jenkins, Franck Cuny, Alberto Simões, Stefan Hornburg, Steven Humphrey, and myself, Sawyer X. Our plans for the next release are to focus on the Dancer command line utility. This does not mean we will ignore everything else, but that we'll be geared towards finishing that aspect that pains us. We've raised various ideas of what we want the command line to be able to do. This includes scaffolding the default (as it does now), perhaps additional example applications, adding more modules, setting some defaults of the frameworks you want to add (Bootstrap, jQuery, etc.), the different configuration options you want, and perhaps some profiles (dzil-enabled, anyone?). We also intend to phase our the "devel" branch in order to clean up the merge and release process and make it easier for new-comers to help out. This might require some changes to forks, but as usual we will be there to help you out and to smooth this transition. In the end, it will be easier for you to submit changes to Dancer and it will be easier for us to review, merge them, and release new versions. Have a wonderful dance, Sawyer X, Dancer core team.

2 1

New Dancer 2 release: 0.07
by sawyer x 04 Aug '13

04 Aug '13

Hey everyone, I would like to get back into the habit of letting everyone know what's going on with Dancer. This means keeping you up to date on releases and our plans for the future. We released Dancer 2 version 0.07 yesterday. This, and the previous release (0.06), represent a sort of awakening in Dancer 2. For a little while you might have felt like the project has been somewhat dormant. It's far from it. Version 0.04 was released on April, and it took three months to get 0.05 out. However, if you take a look at 0.05, you will find it was quite busy: *38 total changes!* There were also many new contributors, which is always very exciting. Version 0.06 saw few changes, but noted interesting and important cleanups, mostly implemented by Franck Cuny. Version 0.07, released yesterday, saw many changes in less than five days. This was due to renewed invigoration by the core team and an improvement in our process. I want to note the importance of Alberto Simões (ambs) taking over the Github issues by storm, setting up milestones, listing the PRs correctly, pinging devs for responses, carrying conversations in the core dev chatroom, and helping out anyone and everyone making sure things keep rolling. Of course this is not to diminish or to miniscule the great help and achievements of so many wonderful people who are listed in the Changes file for every contribution they made or worked with others on. I wish I could buy each and every one of you a beverage! Nuno Carvalho from the Debian Perl Group is keeping us up-to-date with their work on making sure Debian stays up to date, and Debian already has a package out for Dancer2 0.07, less than 24 hours since it was released. Amazing! We have a lot of plans for the future and I'd like to share them, but I think I have already taken much of your time. In the future we intend to write an email and blog post on every release, indicating some of the changes, and noting our plans for future releases. Stay tuned. :) Have a wonderful dance, Sawyer X, Dancer core team.

1 0

Trouble in uploading file
by Fotis E. Psomopoulos 01 Aug '13

01 Aug '13

Dear all, I am quite new to Dancer but I am really amazed on how few lines of code I have to write for the same functionality (still exploring though). However, I have hit the following issue: I am trying to upload a file using the following code: put '/upload/:file' => sub { my $upload_dir = "MyApp/UPLOADS"; my $filename = params->{file}; my $uploadedFile = request->upload($filename); debug "My Log 1: " . params->{file}; debug "My Log 2: " . ref($uploadedFile); open ( UPLOADFILE, "$upload_dir/$filename" ) or die "$!"; while ( <UPLOADFILE> ) { print UPLOADFILE; } close UPLOADFILE; return "DONE"; }; The PUT command is done via cURL as follows: curl --upload-file test http://localhost:3000/upload/test DONE The output that I see in the "development dance floor" is the following: [9072] core @0.000341> request: PUT /upload/test from 127.0.0.1 in /Perl/site/lib/Dancer/Handler.pm l. 56 [9072] core @0.002434> [hit #1]Trying to match 'PUT /upload/test' against /^\/upload\/([^\/]+)$/ (generated from '/upload/:file') in /Perl/site/lib/Dancer/Route.pm l. 84 [9072] core @0.004173> [hit #1] --> got 1 in /Perl/site/lib/Dancer/Route.pm l. 102 [9072] core @0.006625> [hit #1] --> named tokens are: file in /Perl/site/lib/Dancer/Route.pm l. 130 [9072] debug @0.009443> [hit #1]My Log 1: test in MyApp\lib/MyApp.pm l. 20 [9072] debug @0.010818> [hit #1]*My Log 2: in MyApp\lib/MyApp.pm l. 21* [9072] core @0.015854> [hit #1]response: 200 in /Perl/site/lib/Dancer/Handler.pm l. 179 The problem is that the file is created with the correct name in the correct folder (MyApp/UPLOADS/test) but it is always empty (0 size). No other warnings or errors, but I do see an issue in the output (marked in bold - 2nd custom debug line). Any ideas? Thank you in advance for your time! Regards, Fotis -- Fotis E. Psomopoulos PhD, Software Engineer Intelligent Systems and Software Engineering Lab Department of Electrical and Computer Engineering Aristotle University of Thessaloniki Thessaloniki 54124, Greece Phone: +30 2310 99 6349 Fax : +30 2310 99 6398 Email: fpsom(a)issel.ee.auth.gr Site : http://fotis.ee.auth.gr

4 5