Re: mailing list archiver chewing patches

On Tue, Jan 19, 2010 at 09:11, Matteo Beccati <php(at)beccati(dot)com> wrote:
> Il 18/01/2010 18:42, Magnus Hagander ha scritto:
>>
>> On Mon, Jan 18, 2010 at 18:31, Matteo Beccati<php(at)beccati(dot)com>  wrote:
>>>
>>> Il 18/01/2010 15:55, Magnus Hagander ha scritto:
>>>>
>>>> If it wasn't for the fact that we're knee deep in two other major
>>>> projects for the infrastructure team right now, I'd be all over this
>>>> :-) But we really need to complete that before we put anything new in
>>>> production here.
>>>
>>> Sure, that's completely understandable.
>>>
>>>> What I'd like to see is one that integrates with our general layouts.
>>>
>>> Shoudln't bee too hard, but I wouldn't be very keen on spending time on
>>> layout related things that are going to be thrown away to due the
>>> framework
>>> and language being different from what is going to be used on production
>>> (symfony/php vs django/python).
>>
>> I don't know symfony, but as long as it's done in a template it is
>> probably pretty easy to move between different frameworks for the
>> layout part.
>
> By default symfony uses plain PHP files as templates, but some plugins allow
> using a templating engine instead. I guess I can give them a try.

As long as the templating is separated from the code, it doesn't
matter if it's a dedicated templating engine or PHP. The point being,
focus on the contents and interface, porting the actual
HTML-generation is likely to be easy compared to that.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/