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

Dancer 2 and skeleton dir
by Nick Knutov 14 Oct '12

14 Oct '12

Hello, some times ago I wrote about idea of skeleton dir with default dancer app. It's convenient when projects differs from default dancer layout with simple or TT template. For example, in every our project we use only CTPP as templates, CGI::WebIn, which requires some additional strings in hook 'before' by default, etc. Does this feature exists or planned now? -- Best Regards, Nick Knutov http://knutov.com ICQ: 272873706 Voice: +7-904-84-23-130

5 11

Dancer 2 for the masses
by Stefan Hornburg (Racke) 10 Oct '12

10 Oct '12

The core team wants to promote and finalize Dancer 2. IMHO there are a couple of things missing to make it easier for people to try out Dancer 2 and get involved into coding and/or improvements: 1. dancer script and/or sample application for Dancer 2 2. more complete documentation, especially about changes between Dancer 1 / 2 3. updated engines (templates, etc) I unfortunately missed YAPC::Europe 2012, so I couldn't attend the Dancer 2 presentation. Are there any slides available for that presentation? BTW: Which are the assigned coordinators for Dancer 2 (see conference proceedings)? Regards Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team

7 15

Freelance Dancer gig
by sawyer x 07 Oct '12

07 Oct '12

Hey, is anyone looking to pick up a Dancer based freelance gig? Contact joshua.gatcomb(a)gmail.com for more details.

1 0

dancer2's prototype is there, feedback needed
by sukria 05 Oct '12

05 Oct '12

Hi there, I am very glad and proud to announce here that I've came up with a prototype of dancer2 that pleases me enough to be advertised. -*- https://github.com/sukria/dancer2 -*- dancer2 is a complete rewrite of Dancer aiming at providing the same awesomeness with the following major changes: - no more globals in the core - 100% object-oriented backend (based on Moo) - better scoping for sub-applications - better design (no more encapsulation violations, Law of Demeter, ...) The prototype I've pushed to GitHub currently covers ~80% of the DSL of Dancer. It's able to run simple applications (it can run the PerlDancer.org website for instance). Of course, with your real-life applications, it will break in many places in this current shape, and this is where you can help. I'd like to have as many reports as possible regarding upgrades tests. You can test very easily your app with dancer2: $ git clone http://github.com/sukria/dancer2.git $ cd YOUR_APP $ perl -I../dancer2/lib bin/app.pl Also, important to know: most of the plugins may not be working well. Thanks a lot ;)

14 29

"Backup Manager" link in signature - not working
by Assaf Gordon 03 Oct '12

03 Oct '12

Hi, To whoever manages the dancer mailing list: signature contains this link: http://www.backup-manager.org/cgi-bin/listinfo/dancer-users And it doesn't seem to work (unable to resolve DNS 'www.backup-manager.org'). Similarly, the "archives" link here doesn't work: http://lists.perldancer.org/cgi-bin/listinfo/dancer-users -gordon

2 1

Managing "sessions" for each open browser window
by Assaf Gordon 01 Oct '12

01 Oct '12

Hello, Another implementation question for my planned web-site: I want to maintain a "session" (i.e. collection of server-side variables) for each open browser window (not browser "session" in the technical sense). Use-case: 1. a user open a new browser window/tab, goes to my web-site. 2. user changes settings, does some stuff, information is stored for this "session" of open window. 3. same user, same browser, opens a new window/tab, goes (again) to my web-site - now gets a new "empty" session. 4. user changes settings, does some stuff, information is stored for this "session" of open window. 5. the two browser windows (from step 2,4) can be viewed side-by-side, each maintaining independent set of session information. Implementation-wise, I've seen similar web-sites assign a new CGI variable when a user visits the "root" (=landing) page, and propagate that variable in every generated link or HTML form. e.g.: 1. user visits http://myserver.com 2. user redirected to http://myserver.com/?session_id=5 3. from now on, every URL (generated by Dancer's templates) will carry the session ID. 4. if the user opens a new (empty) tab and visists "http://myserver.com" again, he will get "session_id=6" for that window. This seems reasonably easy to implement, but how do I connect the CGI session variable to some sort of Dancer's "session" keyword? I'm thinking of some "before" hook mechanism, but not sure how to go about it... Any suggestions are welcomed, -gordon P.S, I'm aware that a mischievous user could copy&paste the URL to another window, and have two open windows changing the same "session" - I'm not worried by this scenario (as users will be explained that such a thing will simply interfere with their work).

5 9