Hello fellow Dancers! I'm glad to announce that the prototype for Dancer 2 now supports sessions (the YAML session engine is provided and works as expected). So I'd be very happy if you coudl send me upgrade reports of your existign apps (you should be able to run any Dancer 1 app with Dancer 2 now, as long as it doesnt use a plugin that gets into Dancer's core. As usal, to get the code of Dancer 2, go on GitHub: https://github.com/sukria/dancer2 Also, to run the test, you should use the template engine "TemplateToolkit" and the session engine "YAML". You might also need to tweak a bit your config files like the following: in Dancer 1: engines: template_toolkit: ... in Dancer 2: engines: template: template_toolkit: ... Also note that the default start/end tags of TemplateToolkit are back to TT's default in Dancer 2 ([% and %]). Thanks a lot!
On 02/11/2011 11:45, Alexis Sukrieh wrote:
Also note that the default start/end tags of TemplateToolkit are back to TT's default in Dancer 2 ([% and %]).
Are we sure we want that? I agree that it makes things easier for newbies, but <% %> is more editor friendly... :) Cheers
On 2/11/11 10:48 PM, ambs wrote:
On 02/11/2011 11:45, Alexis Sukrieh wrote:
Also note that the default start/end tags of TemplateToolkit are back to TT's default in Dancer 2 ([% and %]).
Are we sure we want that?
I agree that it makes things easier for newbies, but <% %> is more editor friendly... :)
Cheers I agree with ambs, it does make it easier for anyone coming from the rails/sinatra.
Matt
2011/11/2 ambs <ambs+dancer@perl-hackers.net>:
On 02/11/2011 11:45, Alexis Sukrieh wrote:
Also note that the default start/end tags of TemplateToolkit are back to TT's default in Dancer 2 ([% and %]).
Are we sure we want that?
I think so, many many users requested that change since Dancer 1 is born, we never changed it because it was difficult to do such a backward-incompatible change... I think the upgrade of the major version number is a good time to do such a change, it's just a matter of documentaiton. Also, I plan to provide a Dancer::Compatibility module, which will behave as a glue module to make this kind of default changes.
On Wednesday 02 November 2011 11:48:03 ambs wrote:
On 02/11/2011 11:45, Alexis Sukrieh wrote:
Also note that the default start/end tags of TemplateToolkit are back to TT's default in Dancer 2 ([% and %]).
Are we sure we want that?
I agree that it makes things easier for newbies, but <% %> is more editor friendly... :)
[% %], being TT's default, is what a lot of people expected it to be; I heard lots of people being surprised that Dancer made them use <% %> by default instead of the [% %] they were accustomed to. At the end of the day, if anyone does want to use <% %> for some reason, it's an easy configuration change to make it so :)
FYI the bug that made Dancer2 to hang up when processing a POST request with a body is fixed in master. Give it a try again ;) Thanks for your feedback. 2011/11/2 David Precious <davidp@preshweb.co.uk>:
On Wednesday 02 November 2011 11:48:03 ambs wrote:
On 02/11/2011 11:45, Alexis Sukrieh wrote:
Also note that the default start/end tags of TemplateToolkit are back to TT's default in Dancer 2 ([% and %]).
Are we sure we want that?
I agree that it makes things easier for newbies, but <% %> is more editor friendly... :)
[% %], being TT's default, is what a lot of people expected it to be; I heard lots of people being surprised that Dancer made them use <% %> by default instead of the [% %] they were accustomed to.
At the end of the day, if anyone does want to use <% %> for some reason, it's an easy configuration change to make it so :) _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
participants (4)
-
Alexis Sukrieh -
ambs -
David Precious -
Matthew Vickers