[Grok-dev] Grok emerging from the dependencies

[Steve Schmechel]

Thought I would try this out on Windows.
I figured out that I had to install GraphViz.

I still get the following error repeated over and over

  operable program or batch file.
  '.' is not recognized as an internal or external command,

And it generates a bunch of zero-length SVG files in various directories.

I'm not familiar with depgraph or GraphViz.

Is there another missing dependency?

Thanks,
Steve

--- On Tue, 4/27/10, Martijn Faassen <faassen at startifact.com> wrote:

> From: Martijn Faassen <faassen at startifact.com>
> Subject: Re: [Grok-dev] Grok emerging from the dependencies
> To: grok-dev at zope.org
> Date: Tuesday, April 27, 2010, 10:18 AM
> Hi there,
> 
> Another task for those who'd like to help free Grok from
> dependencies:
> 
> Grok depends on zope.app.pagetemplate. When I remove this
> from the 
> dependencies, viewlets fail to work. Figure out why?
> Something gets 
> registered by zope.app.pagetemplate or a dependency of it
> that doesn't 
> get registered and should be. What is it? Could it be moved
> within the 
> ZTK? Let us know.
> 
> Grok depends on zope.app.publisher. When I remove this from
> the 
> dependencies, there is a problem with XMLRPC. Could we move
> the XMLRPC 
> code to zope.publisher perhaps?
> 
> It's easy enough to do this kind of research yourself:
> 
> Run bin/graph-depgraph. This produces a graph of the
> dependencies of 
> Grok in SVG format. With firefox, go to
> parts/depgraph/grok/spec.svg to 
> see it (zoom you a bit). You can now look at Grok's
> dependency graph.
> 
> Identify something that looks like it might be removable.
> Remove it from 
> the configure.zcml. Remove it from setup.py. Possibly add
> the 
> dependencies of the thing you're going to remove to both
> places. Re-run 
> buildout.
> 
> Run the tests. If 1 test fails (the exception view test)
> (the same test 
> as what you get before making any changes), we're good.
> Check in with 
> the dependency removed, repeat.
> 
> Of course, often enough you'll run into a snag. In that
> case you will 
> need to start examining the package in question and
> possibly move things 
> around in ZTK. But even just reporting your conclusions
> here is helpful. 
> Let me know if you need any help.
> 
> Regards,
> 
> Martijn
> 
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>