[Grok-dev] Re: sprint mini-report 2
kevin at mcweekly.com
Fri May 2 14:37:32 EDT 2008
Martijn Faassen wrote:
> Kevin Smith wrote:
>> My judgment is that the spaghetti-traversal mechanism hasn't had
>> enough real use in the wild to expose
>> it's shortcomings.
>> In any case, I think this is an important area of Grok that reequires
>> further exploration.
> Yes, which is what we're trying to do with grok.traversable, of
> course, too. That's not to exclude other explorations, of course.
> grok.traversable does codify patterns I've at least seen in some
> real-world applications.
It showed up for me when I had to show views of my objects in both it's
natural hierarchy *and* in a completely different hierarchy to meet
> What exactly made spaghetti traversal "spaghetti" and what exactly
> wasn't scalable? I think you are talking about complexity scalability,
Yes, complexity scalabilty.
> Perhaps we can see 'grok.traversable()' as a degenerate case of the
> trails approach. Or the other way around, perhaps there are ways to
> expand grok.traversable to do trails-like things.
Yes, I think there is room to expand grok.traversable to do trails-like
> Grok-dev mailing list
> Grok-dev at zope.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Grok-dev