[ add dancer-users@perldancer.org in CC ] Le 15/06/2010 09:14, igor.bujna@post.cz a écrit :
Hello,
Hello, First of all, please post this kind of question directly to the users mailing list, that way more people give attention to your problem and the better the support you get.
sory for my bad english first. I try yours super framework and for me is missing than global vars for template. I wanna defined something in before{} func and this will be in every template. Forr me is simplest show how i use. I call this as 'private_template' and its must be vars like that:
set private_template => '1'; before sub { var private_template => { test => "Hello world", }; };
I must make this patch for Dancer/Helper.pm --- Dancer/Helpers.pm~ 2010-06-09 22:37:44.000000000 +0200 +++ Dancer/Helpers.pm 2010-06-10 21:53:29.000000000 +0200 @@ -54,6 +54,12 @@ $tokens->{session} = Dancer::Session->get; }
+ my $pt = exists($options->{'private_template'}) + ? $options->{'private_template'} : setting('private_template'); + if ($pt) { + $tokens->{private} = Dancer::SharedData->vars->{'private_template'}; + } + my $content = Dancer::Template->engine->render($view, $tokens); return $content if not defined $layout;
------------------------------------------------------------------------------------------------------------------------------------------- Now in every template i can use this variables via 'private' call. It must be enabled for every template via set private_template => '1' Or can enabled or disabled separately in options 'private_template' in given using template.
It would be good to make something similar in this framework.
Thank you and make dance Igor Bujna
Well, Franck Cuny has been rewriting a lot our template engiens recently and I'd like to have his point of view on this. My first opinion is that using settings for private template variables is not a good idea. Setting should remain.... setting ;) We also had in mind to provide a new kind of hook, called "before_template" which could process variables before any template is called. So I suppose we should wait for feedback from the team first. Regards, -- Alexis Sukrieh