[Grok-dev] LoginDemo and PlainLoginDemo

Sebastian Ware sebastian at urbantalk.se
Sun Jan 13 18:17:53 EST 2008

It's no magic :)

Go to the [buldout-eggs/] directory and find the package that you are  
interested in. You will usually find the tests in a file called  
[tests.py] or a directory called [tests/]. You might want to explore  
the components file hierarchy.

You might find other useful documentation in any files ending with  
[.txt]. Both doctests and pure docs. There is usually interesting  
information in the [interfaces.py] file as well.

I use a macosx editor called Textmate which allows me to open a  
directory as a "project" and perform a project wide search. By  
searching for an interface or class I usually find the corresponding  
documentation quickly. Without it, finding the good stuff would be a  
royal pain...

I often use the macosx fulltext file search (spotlight) when trying to  
locate in which component a class or interface is defined. Only to  
open the component with Textmate.

Mvh Sebastian

13 jan 2008 kl. 22.57 skrev daniel:

> Hey Sebastian,
> How do you access all these doctests? Are you working with grok from  
> the python shell?
> Also, is there web access to http://svn.zope.org/ so you can browse  
> the contents? When you're interested in an app, I know how to check  
> one out, but is there some easy way of installing it to test it on  
> my local system?
> I think my way of developing with grok might be limited, the only  
> thing I do is write the scripts/templates in an editor and restart  
> zope/grok.
> Thanks,
> On Jan 13, 2008 12:34 PM, Sebastian Ware <sebastian at urbantalk.se>  
> wrote:
> 13 jan 2008 kl. 18.31 skrev Sebastian Ware:
> > from zope.interface import Interface
> > from zope import schema
> > from BTrees.OOBTree import OOTreeSet
> > from logindemo.app import LoginDemo
> import grok
> ...oops :)
> Mvh Sebastian
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
> -- 
> -- Daniel

More information about the Grok-dev mailing list