Re: [SMARTY] thoughts on extensions to smarty
| From: | Dennis Gearon | Date: | Fri, 21 Feb 2003 19:52:09 +0000 |
| Subject: | Re: [SMARTY] thoughts on extensions to smarty | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-8091@lists.php.net to get a copy of this message | ||
more and more projects are using total CMS sytems, of which a templating system is a building
block.
Maybe you're right, the output format should be a realm of the template.
2/21/2003 11:31:29 AM, Monte Ohrt <monte@ispi.net> wrote:
>I don't understand what this accomplishes? Smarty doesn't care if the
>templates are generating HTML, e-mail text, XML. etc. It doesn't really
>matter, you retrieve the content and then your app does something with
>it (send to browser, send e-mail, etc.)
>
>I don't know about cranking non-text data from the templates (.pdf,
>.doc), that seems a bit out of scope for Smarty.
>
>Monte
>
>On Fri, 2003-02-21 at 13:27, Dennis Gearon wrote:
>> I remember some discussions about using smarty to do emails.
>>
>> The general case of a template engine seems to be:
>>
>> (User input + Database)->(business_logic)->(template_engine + template + format ) =
document.format
>>
>> so in the case of smarty, it would be nice if the last line in a file using a smarty object
>>
could
>> be like this:
>>
>> $smarty->display( file.tpl, 'HTML', array() );
>> sends html back to the user.
>> $smarty->display( file.tpl, 'EMAIL', array( email headers ) );
>> sends email back to the user.
>> $smarty->display( file.tpl, 'HTML_IN_EMAIL' array( 'EMAIL' =>
>> array( email headers )) );
>> sends html IN email back to the user.
>> $smarty->display( file.tpl, 'PDF', array( ) );
>> sends PDF file back to the user.
>>
>>
>> etc,etc,etc with .doc, .ps, .csv,
>>
>> Is there any thought to this being done ever?
>>
>--
>Monte Ohrt <monte@ispi.net>
>
>