On Mon, Sep 15, 2008 at 5:59 PM, Thomas Rabaix <[EMAIL PROTECTED]> wrote:
> I am almost ok with this method, but ... > - the set*ContentResolver are ... quite complicated, can it be more > magic, or optional ? Please make suggestions :P Maybe François can help here? > - this should me an sfMail class which handle array as constructor. > This will allow to quickly build an email. Yep, why not > - how can we access to an image reference inside the template ? This feature is provided by Swift: http://www.swiftmailer.org/wikidocs/v3/tutorials/embedding_images So using a symfony template, just pass the image attachment to the template and echo it as the source of the image tag (like the 1.0 way) > one more thing : > The send method should take an optional argument to set the default > mail gateway. (think like database connection definition) Yes, good idea indeed. We should be able to define an optional pool of mailers in the factories.yml config. I saw something similar in the original SwiftMailer lib, I'll check it out. ++ -- Nicolas Perriault http://prendreuncafe.com - http://symfonians.net - http://sensiolabs.com Phone: +33 660 92 08 67 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
