Wichert Akkerman wrote:
> If reimplementing something is easy to do (which is generally true
> considering we all have Zope's source) and allows you to drop all that
> extra baggage that - why not?
Because you have to maintain it forever. Of course, you may not mind
doing that - it'll be a case-
Previously Martin Aspeli wrote:
> Wichert Akkerman wrote:
> > Previously Martin Aspeli wrote:
> >> If you want to pull in, say, plone.supermodel (a "pure Zope 3" package
> >> that should be re-usable and may be useful to BFG if it ever wants to
> >> serialise Zope 3 schema interfaces to/from an X
Paul Everitt wrote:
> On Dec 22, 2008, at 1:06 PM, Martin Aspeli wrote:
>
>> Wichert Akkerman wrote:
>>> Previously Martin Aspeli wrote:
If you want to pull in, say, plone.supermodel (a "pure Zope 3"
package
that should be re-usable and may be useful to BFG if it ever wants
Martin Aspeli wrote:
> Paul Everitt wrote:
>> On Dec 22, 2008, at 6:36 AM, Martin Aspeli wrote:
>>
>>> Chris (and Agendaless) is of course free to do whatever he wants with
>>> BFG. And as I've shown many times, I'm very supportive of the great
>>> work
>>> coming out of the Repoze project.
>>>
>
On Dec 22, 2008, at 1:06 PM, Martin Aspeli wrote:
> Wichert Akkerman wrote:
>> Previously Martin Aspeli wrote:
>>> If you want to pull in, say, plone.supermodel (a "pure Zope 3"
>>> package
>>> that should be re-usable and may be useful to BFG if it ever wants
>>> to
>>> serialise Zope 3 sche
Martin Aspeli wrote:
> Wichert Akkerman wrote:
>> Previously Martin Aspeli wrote:
>>> If you want to pull in, say, plone.supermodel (a "pure Zope 3" package
>>> that should be re-usable and may be useful to BFG if it ever wants to
>>> serialise Zope 3 schema interfaces to/from an XML representati
Paul Everitt wrote:
> On Dec 22, 2008, at 6:36 AM, Martin Aspeli wrote:
>
>> Chris (and Agendaless) is of course free to do whatever he wants with
>> BFG. And as I've shown many times, I'm very supportive of the great
>> work
>> coming out of the Repoze project.
>>
>> However, if Repoze is aimin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> Wichert Akkerman wrote:
>> Previously Martin Aspeli wrote:
>>> If you want to pull in, say, plone.supermodel (a "pure Zope 3" package
>>> that should be re-usable and may be useful to BFG if it ever wants to
>>> serialise Zope
Wichert Akkerman wrote:
> Previously Martin Aspeli wrote:
>> If you want to pull in, say, plone.supermodel (a "pure Zope 3" package
>> that should be re-usable and may be useful to BFG if it ever wants to
>> serialise Zope 3 schema interfaces to/from an XML representation) well,
>> it uses zope:
Martin Aspeli wrote:
> repoze.zcml is a symptom that an improvement is needed further down the
> stack. In the Plone world, we've learned the hard way that rolling your
> own to avoid having to push something deeper into the stack is a costly
> strategy in the long run. Paul should certainly kn
On Dec 22, 2008, at 6:36 AM, Martin Aspeli wrote:
> Chris (and Agendaless) is of course free to do whatever he wants with
> BFG. And as I've shown many times, I'm very supportive of the great
> work
> coming out of the Repoze project.
>
> However, if Repoze is aiming to bridge the gap between t
Previously Martin Aspeli wrote:
> If you want to pull in, say, plone.supermodel (a "pure Zope 3" package
> that should be re-usable and may be useful to BFG if it ever wants to
> serialise Zope 3 schema interfaces to/from an XML representation) well,
> it uses zope:* ZCML directives. Are you goi
Tres Seaver wrote:
> Note that one change I would make to the docs is to make using the 'bfg'
> namespace *not* the default in the examples; marking each non-Zope
> directive with 'bfg:' (in the examples, not necessarily in a real-world
> config) would remind people, "this is not your father's Ol
Mmmm... I didn't mean for this to get quite so emotional. :)
Chris (and Agendaless) is of course free to do whatever he wants with
BFG. And as I've shown many times, I'm very supportive of the great work
coming out of the Repoze project.
However, if Repoze is aiming to bridge the gap between th
14 matches
Mail list logo
