[Grok-dev] grok, content and grokcore

[Martijn Faassen]

Jan-Wijbrand Kolman wrote:
> Souheil CHELFOUH <trollfot at gmail.com> wrote:
>> I'm currently working on a purification of dolmen.content
>> The package currently relies on the big Grok package, for the content
>> component, Model, Container, Ordered Container.
>> Do you guys think that these components could be factored out into a
>> grokcore package ?
>> something like grokcore.content or megrok.content ? This would include
>> Model, Container and OrderedContainer
>> These classes are not tightly tied to any other component.
>>
>> I'm willing to do that surgical cut if you think it's worthy :)
> 
> I'm not sure what this would bring us? To what extend are Model and 
> Container and OrderedContainer really reusable by others? In what way 
> would it make the Grok package itself cleaner?

There are a few minor benefits:

* you could theoretically use a package that depends on grokcore.model 
with a plain Zope 3 app or Zope 2.

* it's also easier to remix grokcore.* packages together into a "new 
Grok", imagining experiments with the publisher, etc.

* it's easier to control dependencies.

* you can test your own package's content types in more isolation than 
if you depend on the full Grok.

These benefits are probably minor, but together they weigh heavily 
enough to go ahead and do it. That reminds me of megrok.traject, which 
needs grok.Traverser and therefore needs to depend on the full grok. 
Perhaps another candidate for an extraction project..

Regards,

Martijn