2008/9/17 Nicolas Perriault <[EMAIL PROTECTED]>:
> And it will allow to set vars for the
> whole email class and to having to pass them every time like this:
Not sure I get you.
Does in mean that you define one single action (mail/foo), and symfony
(1.1) uses its multiformat support to render both a text and an HTML
part? That might be possible if the templates dir of the mail module
looked like:
modules/mail/templates/
_foo.txt.php
_foo.html.php
That wasn't explicit in your RFC, so I'm not sure.
My proposal of using the already available partial/component helpers
(or an OO equivalent) decouples the sfMail class from the symfony view
layer and relies on current knowledge, without introducing new class
constants or classes. If the tradeoff is to have to define explicitely
both parts and set a variable before to give html and text parts the
same array of arguments (that's two lines of code), that's a price I'm
willing to pay.
You are already going way further than what Django or Rails propose. I
think KISS is the objective here.
François
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
