Class HtmlMail

You pass in a CleverCSS template (it'll be run through the template engine before CleverCSS), the html_template, and any variables that the CSS template needs.

The CSS template is processed once, the html_template is processed each time you call render or respond.

If you don't like markdown, then you can set the wiki variable to any callable that processes your templates.

Overrides: object.__init__

If you want to change the CSS, simply call this with the new CSS and variables. It will change internal state so that later calls to render or respond use the new CSS.

Used mostly internally to find all the tags that fit the given CSS selector. It's fairly primitive, working only on tag names, classes, and ids. You shouldn't get too fancy with the CSS you create.

Used mostly internally but helpful for testing, this takes the given HTML and applies the configured CSS you've set. It returns a BeautifulSoup object with all the style attributes set and nothing else changed.

Works like lamson.view.render, but uses apply_styles to modify the HTML with the configured CSS before returning it to you.

If you set the pretty=True then it will prettyprint the results, which is a waste of bandwidth, but helps when debugging.

Remember that content_template is run through the template system, and then processed with self.wiki (defaults to markdown). This let's you do template processing and write the HTML contents like you would an email.

You could also attach the content_template as a text version of the message for people without HTML. Simply set the .Body attribute of the returned lamson.mail.MailResponse object.

Works like lamson.view.respond letting you craft a lamson.mail.MailResponse immediately from the results of a lamson.html.HtmlMail.render call. Simply pass in the From, To, and Subject parameters you would normally pass in for MailResponse, and it'll craft the HTML mail for you and return it ready to deliver.

A slight convenience in this function is that if the Body kw parameter equals the content parameter, then it's assumed you want the raw markdown content to be sent as the text version, and it will produce a nice dual HTML/text email.