[Grok-dev] Grok and chameleon
wichert at wiggy.net
Mon Feb 8 04:50:13 EST 2010
People are using five.pt and grokcore.* in production systems, so it is
not too early at all. Apparently sometimes innovation happens earlier in
Zope 2 ;)
On 2010-2-8 10:46, Souheil CHELFOUH wrote:
> That's probably a bit early to start and argue about back compatibility.
> Let's try and do the best option for Grok and see how we can get some
> backward compatibility.
> We do not want to get stuck, obvisouly, nor to burn bridges around us :)
> So, let's get started with the chameleon integration already !
> 2010/2/8 Sylvain Viollon<sylvain at infrae.com>:
>> On Sat, 06 Feb 2010 14:59:35 +0100
>> Martijn Faassen<faassen at startifact.com> wrote:
>>> I think we should be careful with this stuff. That is, we should
>>> definitely allow a profile of grokcore.view that uses the
>>> zope.pagetemplate implementation. That should be fine with Zope 2.
>>> In general the whole concept that "we can't do this because Zope 2 is
>>> using Grok stuff" worries me a little as we might end up in the "too
>>> many different stakeholders to move anywhere" situation all too
>>> easily. So while I appreciate the input, and I'm going to listen to
>>> it, I'd be against letting it weigh so heavily that Grok cannot
>>> evolve forward anymore.
>> I don't have any problem with that change. I think it might conflict
>> with people using five.pt, maybe, but I don't. I use
>> megrok.chameleon, where I want Chameleon templates (explicitly).
>> Sylvain Viollon -- Infrae
>> t +31 10 243 7051 -- http://infrae.com
>> Hoevestraat 10 3033GC Rotterdam -- The Netherlands
>> Grok-dev mailing list
>> Grok-dev at zope.org
> Grok-dev mailing list
> Grok-dev at zope.org
Wichert Akkerman <wichert at wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
More information about the Grok-dev