Grok Grok: Now even cavemen can use Zope 3!
Download

Grok Ranking & Summary

Grok Tags

Python Python module Zope objects Zope applications use Zope

Grok Description

Grok: Now even cavemen can use Zope 3! What is grok?Grok is a Python tool that makes it easier to get started with a Zope 3 web application.Grok uses the Component Architecture and builds on Zope 3 concepts like content objects (models), views, and adapters. Its simplicity lies in using convention over configuration and sensible defaults when wiring components together. That means neither a configuration language like ZCML nor a lot of repetition are needed to create a web application with grok.You can find out much more about Grok at our http://grok.zope.org website.Who is grok?Grok is a friendly caveman from the Stone Age. He has a big club that he hunts mammoths with. He will also use this club to smash anything he doesn't like."ME GROK SMASH ZCML!"Getting grokThe easiest way to get started with grok is to install the grokproject package (e.g. via easy_install grokproject) and then create a new project area by calling the grokproject script like so:$ grokproject MyProject... many lines of output hereThis will create a project area in MyProject as well as download and install grok and Zope 3 (the application server grok is built on).You can also get grok from the subversion repository:svn co svn://svn.zope.org/repos/main/grok/trunk grokThen follow the instructions of INSTALL.txt. Requirements: · Python What's New in This Release: · Revert back to an older version of grokui.admin that has not seen any changes related to the grok.View permission and the View/CodeView split and still has the introspector that is removed from newer versions. · grokcore.view, grokcore.viewlet and grokcore.formlib and Grok itself have been updated to undo the View/CodeView split that we had temporarily introduced in the development versions after Grok 1.0a4. This means the behavior of grok.View is unchanged from Grok 1.0a4. Nothing to see here! · Changed the default permission to zope.View instead of zope.Public. This means a modification needs to be made to your site.zcml if you're upgrading an existing Grok-based project. See the upgrade notes for more information. · Bump used zope.app.wsgi version (now: 3.4.2) to support product-configs in zope.conf files with paster. · Default location for Data.fs and logfiles of grok's sample application is now var/filestorage/ and var/log/ instead of parts/data/ and parts/log/. · Bump used z3c.testsetup version (now: 0.4). · Bump used ZODB3 version (now: 3.8.3). · Added zope.publisher.interfaces.IReRaiseException adapter for IUnauthorized exceptions. · Removed docutils and Pygment from versions.cfg. Both are pinned in grokdocs subpackage. · Corrected Content-type; JSON views now report 'application/json'. · updated zope.publisher dependency to 3.4.8 (fix paster.httpserver related bugs in XMLRPC, PUT) · switched buildout to paster based template (like grokproject default) · changed interpreter name from 'python' to 'grokpy'. · Restructured the upgrade and change documentation so that they now get generated into separate files by Sphinx

Grok Related Software