[Grok-dev] megrok.layout --> grokcore.layout and megrok.chameleon --> grokcore.chameleon

Martijn Faassen faassen at startifact.com
Fri Jul 15 10:23:20 EDT 2011

On 07/15/2011 02:22 PM, Jan-Wijbrand Kolman wrote:
> On 15/07/2011 13:56 , Martijn Faassen wrote:
>> How does this affect the future of grokcore.viewlet? Is this competing
>> with grokcore.layout now?
> Viewlets do not at all compete with Layout components. Layout components
> "compete" with the tradtional ZPT macros. Viewlets and other content
> provider can be used perfectly fine when using the Layout and Page
> components.

Would be nice to have some sort of guide which points people in the 
right direction.

>> I think for future steps we need to make progress on two topics we
>> identified during the last sprint:
>> * a grok core that is okay with dropping selective dependencies
>> (conditionally importing them for convenience reasons)
> The chameleon and layout dependencies now indeed will be pulled in
> whether or not you're using them. And indeed we need to figure out a
> robust way for these "conditional" imports.
> I just thought in this case it was OK not to have to invent that
> conditional-import mechanisms before I could add these component that
> quite some Grok projects use.

Sure, I agree. I think this is progress, and progress is good!

That's why I'm talking about future steps.



More information about the Grok-dev mailing list