Hi Fabien,

In it's current implementation, yes. I could also see an adapted
implementation where one could specify which template the parameter
was for, but in this specific information I had a single template for
a page, and just needed to register parameters for that page in a
distributed way through the engine object, so my initial patch did
it's job.

Stefan

On Tue, Oct 6, 2009 at 11:01 PM, Fabien Potencier
<[email protected]> wrote:
>
> Stefan Koopmanschap wrote:
>> Hi all,
>>
>> I just created ticket #7292
>> (http://trac.symfony-project.org/ticket/7292) with a proposal for the
>> addition of a setParameter method in the sfTemplateEngine class of the
>> Templating component. As I was working on some code where I wanted to
>> introduce the symfony Templating component, I was in a situation where
>> it meant some dirty work (well, considering the existing codebase) to
>> get all parameters to the render() method. Instead, I just wanted to
>> register the parameters bit by bit to the sfTemplateEngine object,
>> which was available throughout the places where the values for
>> parameters were set. The implementation as attached to the ticket did
>> just what I needed, and I suspect I am not the only one that would
>> come into situations where this would be useful.
>>
>> I would like some feedback. Given that I am quite new to the
>> Templating component, have I overlooked an existing way of doing this?
>> If not, is my solution a good solution?
>
> IIUC, you want to introduce global parameters, accessible from all
> templates?
>
> Fabien
>
>>
>> Sincerely,
>>
>
> >
>



-- 
Stefan Koopmanschap
Symfony Community Manager
[email protected]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to