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

Can I convert App::Notifier::Service from Dancer 1 to Dancer2?
by Shlomi Fish 07 Aug '15

07 Aug '15

Hi all, Is there a good reason why I should *not* convert https://metacpan.org/pod/App::Notifier::Service from Dancer 1 to Dancer2? It's a simple web app, meant to run synchronously, and I can debug it by using perl -d, and last time I tried doing s/Dancer/Dancer2/g everything worked nicely. Is there a good enough reason to stay with Dancer 1? Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ http://www.shlomifish.org/humour/bits/Can-I-SCO-Now/ - "Can I SCO Now?" If it isn’t in my email, it doesn’t exist. And if the whole world says one thing and my email says something different, email will conquer. — an Israeli Linuxer. Please reply to list if it's a mailing list post - http://shlom.in/reply .

6 7

Appdir and 0.150000
by Cymon 30 Aug '14

30 Aug '14

Hi all, develping my package, Strehler, I usually write my test using a little testing app under /t and running everything throught Test::TCP. You can see all the code in my github: https://github.com/cym0n/strehler (src/t) This worked well until I tried it on Dancer2 0.150000. In this case the system seems to do a lot of confusion about appdir so it can't read the config.yml under t/testapp and breaks all. Behaviour of Dancer2 in this situation can be considered an anomaly or depends on something I did wrong? There's a way smarter than mine to manage a dummy app for testing purpose? A dummy app complex as I like... Thanks, -- Cymon http://perlishscrewdriver.blogspot.it/

1 1

send_file and exit of route handler
by Andrew Beverley 28 Aug '14

28 Aug '14

Hi guys, Dancer2::Manual contains some contradictory information about whether a "return" is needed when using send_file. The second paragraph states that a return is no longer needed, but the end of the section states that one should always be used. In the past I found that it wasn't needed. However, having recently upgraded to v0.15, the behaviour /seems/ to have changed and I've had to add it back in. Has something changed or should return always be used anyway? Thanks, Andy

1 0

Perl::Dancer Conference 2014 - Call for Papers
by Stefan Hornburg (Racke) 25 Aug '14

25 Aug '14

The Perl::Dancer Conference will be held in Hancock, NY on the 8th and 9th October. In addition we are having professional tutorials on the 6th and 7th October. We are interested in hearing about your talks in the following topics: Session types are 20 minutes (short talks), 40 minutes (regular talks) and 2 hours for tutorials. Submissions are due before midnight (23:59 EST) on 11th September. Please check out http://act.perl.dance/eic2014/cfp.html for more detailed information about this call for papers or contact us at 2014(a)perl.dance. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2014: http://act.perl.dance/

1 0

Retrieving params of fields with multiple values
by Andrew Beverley 24 Aug '14

24 Aug '14

Hi guys, I may be missing something here, so I wanted to run this by you: When a form is submitted that has multiple fields with the same name (such as several checkboxes), the values of that field are all returned in an array ref. However, if the same form is submitted, but only one value is returned (eg. only one checkbox has been ticked) then a scalar is returned. If no checkboxes are ticked, then undef is returned. This makes it difficult to process a form with several checkboxes, as the return value from param('checkbox') can be an array ref, scalar or undef, depending how many checkboxes are ticked. At the moment, I'm testing for each of those 3 conditions. Is there a better way? It would be useful if param() could be called in array context, in which case it would return 0, 1 or several items, depending on which ones were checked. Thanks, Andy

5 9

@Champoux
by Henk van Oers 24 Aug '14

24 Aug '14

Thank you for the shower :-)

1 0

Dancer2 + Dist::Zilla
by Jens Rehsack 20 Aug '14

20 Aug '14

Hi, Intro: As David and Leon recommended, I give Dist::Zilla as authoring tool a chance ;) We (read: Florian guided by me) create a service monitor for an embedded device. This service monitor needs to be cross-compiled (sounds trivially in case of a Perl module and is for sure easier than for a Go software - but not plain copy) to become part of a compressed, read-only rootfs. "dzil build" / "dzil release" (w/o pause info) creates a smooth tarball which includes every nice bit we want to deploy (even public, scripts and views). Question: The Makefile.PL (and the resulting Makefile) in the distfile doesn't care about public and views. How can dzil be pleased to generate a Makefile.PL caring about those directories? (I thought better ask before reverse-engineer D::Z::P::ShareDir ^^) Cheers -- Jens Rehsack rehsack(a)gmail.com

1 0

Dancer2 0.150000 - Codename LoonyPandora
by sawyer x 20 Aug '14

20 Aug '14

Hi everyone, yesterday we released the long-awaited version 0.150000 of Dancer2. *Codename LoonyPandora:* This release is dedicated to our colleague and friend James Aitken (otherwise known as LoonyPandora) who had recently passed away, having been struck by a vehicle. James was a contributor to Dancer (both 1 and 2) since the early age of these projects. He provided insight, fixes, plugins, and was a crucial part of the community. His many contributions have made Dancer better, but his personality, charm, and warmth are at the heart of our community. We are eternally grateful for the light we received with his presence, and we will remember him kindly. Thank you, James, from all us. *Changes in this release:* It took us a while to release this version because it carries a few massive changes. These introduce some incompatibility (which we're trying to help with, and reduce using shims), but also solidifies the structure of the architecture. ** Context is removed:* The biggest change in this release is the untangling and removal of the context object of Dancer2: Dancer2::Core::Context. Contexts are useful (providing all the... well, context of a request), but the way it was implemented in Dancer2 was tricky. It was complicated, global, had state that wasn't easily removed, existed in multiple places across the code, and not just a source of pain, but also a memory leak we had only fixed when removing it. We might introduce it back again, but this time we will be able to do it much better, if need be. This change introduces a possible problem for other plugins. We will try to follow all the plugins available and help release new versions of these plugins in order to accommodate this change. Please bear with us. We will also appreciate any help to get this done as soon as possible. ** App-specific PSGI application:* Another big change is the ability to create full-fledged PSGI apps from specific Dancer Apps, instead of all the available Dancer Apps. This is an important difference to understand. When you call "start", "dance", or "Dancer2->psgi_app()", it will generate a PSGI app from all the available Dancer Apps. This means every App loaded ("use MyApp") will be part of the PSGI app we generate. However, you can now create both PSGI apps from a single Dancer App, but also from multiple Dancer Apps - which can be defined by name or regular expression: # load three Dancer Apps in memory use App1; use App2; use App3; # create a PSGI app from all of them my $psgi = dance; # or start # create a PSGI app from App3 alone: my $psgi = App3->psgi_app; # create a PSGI app from both App2 and App3: my $psgi = Dancer2->psgi_app( [ 'App2', 'App3' ] ); # create a PSGI app from both App1 and App2 using regular expressions: my $psgi = Dancer2->psgi_app( [ qr/^App(1|2)$/ ] ); This feature allows you to preload every Dancer App, without forcing a PSGI app of all of them. This is exceptionally useful in a large environment with multiple apps loaded into memory providing separate PSGI apps used by the user. ** Major memory leaks fixed:* Thanks to the context untangling and additional work by Russell Jenkins, we have removed multiple memory leaks that have been annoying us for quite some time. ** App-specific configuration:* We can now define specific configurations using a separate configuration file for each Dancer App. This involved a lot of work of untangling the configuration role. Take a look at t/config_multiapp.t test and the associated sample Dancer Apps as an example of how this works. ** Various fixes and improvements* We have also made some changes, closing additional 14 issues, and multiple fixes and enhancements which weren't covered in tickets. The following people are responsible for this release (in alphabetical order): Andrew Solomon, Andy Jack, Bas Bloemsaat, Chunzi, DavsX, Ivan Kocienski, Javier Rojas, Jean Stebens, Michał Wojciechowski, Mickey Nasriachi, Pedro Bruno, Russell Jenkins, Sawyer X, Stefan Hornburg, Steven Humphrey. Way to go, everyone! :)

3 7

Sad news regarding James Aitken (LoonyPandora), Dancer contributor and pluign author
by David Precious 18 Aug '14

18 Aug '14

Hi all, Sadly, my friend and colleague James Aitken (LoonyPandora/JAITKEN), who contributed to Dancer and wrote several Dancer plugins, died unexpectedly last week. He was hit by a car back in June and suffered head injuries, but had mostly recovered - but then took a sudden turn for the worse, and passed away last week. Details as to exactly what happened are still sketchy at this point. Due to how unexpected it all was and the fact he has no immediate family / next of kin, he will receive a very very basic state-funded "pauper's funeral" unless enough money is raised to cover the cost of a proper funeral - so his ex-girlfriend set up a fundraising page to accept donations towards the cost: http://gogetfunding.com/project/james-aitken-s-funeral If you used his code and found it useful, and have a couple of quid to spare, any donations would be very much appreciated. If you cannot, but he or his code made a difference to you, you can still leave a comment there if you'd like. 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

5 5

can not quick_delete on sqlite ?
by Tonton 11 Aug '14

11 Aug '14

Hello i use a db file per entreprise of user in my dancer app, i can get insert and update but for delete it is not really works...:( this how i do that the table have primary key name id my $dbname = "$UPLOAD/$entreprise/$entreprise.sqlite"; database({ driver => 'SQLite', database => $dbname })->quick_delete('fournisseurs', {id => $idFourToDel} ); is someone with solution or same trouble T.

1 1