All Content Updates

SUBJ1

Royaryshoma — 2011-10-21T00:10:43Z

SUBJ1nisse

Grok 1.4 released!

jw — 2011-04-04T15:27:45Z

Grok 1.4 is a feature release of Grok based on the Zope Toolkit 1.1.1.

The Grok development team is happy to announce the Grok 1.4 release!

This release brings several new features and bugfixes.

The list of Grok specific package version can be found here:

http://grok.zope.org/releaseinfo/1.4/versions.cfg

To upgrade existing project you might find the upgrade notes helpful, to be found here:

http://grok.zope.org/doc/1.4/upgrade.html

Amongst other changes, Grok 1.4 brings:

New features in grokcore.view like allowing for the use of the grok.provides() directive in view components, the addition of a grok:ignoreTemplates ZCML directive to configure what template filename extensions are to be ignore when reporting unassociated templates, improved reporting of unassociated templates and improved grok.template() directive inheritance.

New Subscriptions and MultiSubscriptions components from grokcore.component

Includes the latest zope.testbrowser version that is based on WebOb and WebTest.

Besides working on code, the Grok community is also working on improving the documentation, both the "official" documentation and the "community"-driven efforts. This is quite an undertaking and not yet finished.

1.4

jw — 2011-04-04T14:54:57Z

Grok 1.4 is a feature release

0.10.1

kteague — 2011-01-24T14:41:22Z

Release to fix the dependency problems of the versions of installed packges.

Grok Releases

kteague — 2011-01-24T14:27:10Z

Information about new features, changes and bug fixes for releases of Grok.

Download

kteague — 2011-01-24T14:00:40Z

How to download and install Grok for the first time

Get started with Grok!

Grok is easy to get started with, only a few common dependencies need to be fulfilled before you install Grok. These dependencies are Python 2.7 or Python 2.6 (Python 2.5 will work too), a C compiler, and Easy Install. Once you've met those requirements, you will install a program called grokproject which will automatically download and install Grok and create a bare bones layout for a brand new Grok project.

Python

Python is a dynamic object-oriented programming language. It's clear, readable syntax combined with a robust, mature implementation means that it's suitable for a wide variety of problems. The Grok developers believe it makes an ideal web development language, combining both programmer productivity and long term maintainability.

C Compiler

Grok is built on top of the Zope Toolkit. For performance reasons, portions of the source code are written in C. On platforms such as Linux or Mac OS X, you don't have to worry about this as the installer will compile and build these bits for you during installation. You will need a working C compiler installed on your system. On Windows, binary packages will be automatically installed for you (if you use Python 2.6) so there is no need for a C compiler.

If you are using Mac OS X, you can install gcc compiler by install the Developer Tools package that is available on your Mac OS X operating system DVD.

N O T E : XCode 3.2 which comes with Mac OS X 10.6 won't compile C-code from older Zope eggs out of the box. If you run into this problem, install XCode 3.0.

Easy Install

Easy Install is a python module that lets you automatically download, build, install, and manage Python packages. Download and run a simple Python script called ez_setup.py to install the easy_install program into your Python 2.x install. You can read more about this on the PEAK Easy Install page.

$ python2.x ez_setup.py

Some systems such as Mac OS X use the sudo command to allow you to install programs as the root user. This is required if you are using a system installed version of Python 2.6.

$ sudo python2.6 ez_setup.py

It may be that you have Easy Install already available but a version that is too old. You can upgrade it by giving it the -U option:

$ sudo easy_install -U setuptools

VirtualEnv

NOTE: As of Grok 1.2, you do not need to use virtualenv. Grok is automatically isolated from the system python environment.

Virtualenv is a python tool that allows you to create isolated python environments. It's not a requirement for installing Grok, but installing grokproject globally does add a few new packages to your system Python's site-packages. If you are installing Grok to use as a developer sandbox, these packages can interfere with existing versions of those Python packages already available on your system. You can read more about using VirtualEnv to create a clean Grok installation.

Grok Project

Grok Project let's you create new Grok-based applications. It's a scaffolding tool for generating an installer for your application and a bare bones layout of a new Grok-based Python project. You can install Grok Project with easy_install, then run it, answer a few questions about the project you'd like to create, and it will generate a new ready-to-go directory named after your project.

$ easy_install grokproject
$ grokproject mygrokprojectname

Currently running grokproject downloads the parts required to build a complete Grok installation from a number of different sources over the internet. If during installation you see a 'Connection reset by peer' error message such as:

Error: Download error for
http://wwwsearch.sourceforge.net/mechanize/src/mechanize-0.1.7b.zip: (104,
'Connection reset by peer')

Then you can either re-run grokproject, or change into the newly created project directory and repeatedly run './bin/buildout' until buildout manages to download all of the necessary packages. In the future we hope to bundle all of the individual parts of Grok together to solve these installation hiccup problems.

Learn Grok

Now that you've got Grok installed with a bare bones project, you can start learning about Grok with the Grok Tutorial. Or you can browse or search the Grok Documentation area of this web site if you are looking to find help with a specific task.

Additional import needed

anil — 2011-01-24T07:19:04Z

Additional import needed

Import change with zope.formlib 4

anil — 2011-01-21T08:49:33Z

Import change with zope.formlib 4

Change in grok.Fields?

anil — 2011-01-21T08:44:37Z

Change in grok.Fields?

Grok 1.3 released!

jw — 2011-01-20T21:36:49Z

Grok 1.3 is a feature release of Grok based on the Zope Toolkit 1.1c1.

The Grok development team is happy to announce the Grok 1.3 release!

Where the previous release was mostly about slimming down the dependency hierarchy of packages that comprises Grok, this release brings several important changes in functionality typically found Grok-based applications.

Grok 1.3 is based on the Zope Toolkit 1.1c1 release!

Since the ZTK 1.1 release drops Python-2.4 support and gains Python 2.7 support, it was able to update quite a number of packages, most notably the ZODB. Grok does currently not need to override any version of packages defined in the ZTK!

The list of Grok specific package version can be found here:

http://grok.zope.org/releaseinfo/1.3/versions.cfg

To upgrade existing project you might find the upgrade notes helpful, to be found here:

http://grok.zope.org/doc/1.3/upgrade.html

Amongst other changes, Grok 1.3 brings:

The long awaited support for the most recent martian version.

The long awaited merge of the template registry refactoring. This should result in considerable less spurious warnings concerning unassociated templates.

Integration of the Fanstatic library and WSGI components. From the Fanstatic website:

""" Fanstatic is a small but powerful framework for the automatic publication of resources on a web page. Think Javascript and CSS. It just serves static content, but it does it really well. """

The "static" directory functionality in Grok based projects is now based on Fanstatic and the compatibility layer provided by zope.fanstatic.

Removal of the automatic test discovery and registration that was provided by the z3c.testsetup package. For newly created projects, the grokproject tool will layout examples of setting up test suites. Note that this is a first step in the way towards more drastic improvements in regards to test discovery and running tests.

Other important notes:

The updated grokproject tool will not be able to build new project based on Grok version < 1.3.

Besides working on code, the Grok community is also working on improving the documentation, both the "official" documentation and the "community"-driven efforts. This is quite an undertaking and not yet finished.

We realize this release will again bring quite some structural changes that might affect your projects in some way. Please let us know when you run into problems upgrading your projects on the grok-dev mailinglist or on the #grok IRC channel. We will try to help and it will also help us, the Grok developers, by fixing bugs and other issues.

1.3

jw — 2011-01-20T21:36:52Z

Grok 1.3 is a feature release of Grok based on the Zope Toolkit 1.1c1.

The Grok development team is happy to announce the Grok 1.3 release!

Grok 1.3 is based on the Zope Toolkit 1.1c1 release!

The list of Grok specific package version can be found here:

http://grok.zope.org/releaseinfo/1.3/versions.cfg

To upgrade existing project you might find the upgrade notes helpful, to be found here:

http://grok.zope.org/doc/1.3/upgrade.html

Amongst other changes, Grok 1.3 brings:

The long awaited support for the most recent martian version.
The long awaited merge of the template registry refactoring. This should result in considerable less spurious warnings concerning unassociated templates.
Integration of the Fanstatic library and WSGI components. From the Fanstatic website:

""" Fanstatic is a small but powerful framework for the automatic publication of resources on a web page. Think Javascript and CSS. It just serves static content, but it does it really well. """

The "static" directory functionality in Grok based projects is now based on Fanstatic and the compatibility layer provided by zope.fanstatic.

Removal of the automatic test discovery and registration that was provided by the z3c.testsetup package. For newly created projects, the grokproject tool will layout examples of setting up test suites. Note that this is a first step in the way towards more drastic improvements in regards to test discovery and running tests.

Other important notes:

The updated grokproject tool will not be able to build new project based on Grok version < 1.3.
Besides working on code, the Grok community is also working on improving the documentation, both the "official" documentation and the "community"-driven efforts. This is quite an undertaking and not yet finished.

How to get started with Dolmen

fretin — 2011-01-11T10:56:45Z

Dolmen is set of libraries to create a CMS. You will learn how to get started with Dolmen.nisse

Grok Forums

kteague — 2010-12-24T08:47:52Z

Nabble provides a web interface to the Grok mailing lists.Grok

Install Grok on MS Windows

rogererens — 2010-11-04T14:51:04Z

This HowTo gives instructions for installing Grok on the various flavours of MS Windows. Please note that this HowTo is a _WORK IN PROGRESS_ during the alpha releases of Grok version 1.0 and grokproject version 1.0. TBD denotes To Be Discussed/Determined/Developed/Described/Donenisse

Using Virtualenv for a clean Grok installation

dcarraher — 2010-11-04T14:50:44Z

NOTE: As of Grok 1.2, you do not need to use virtualenv. Grok is automatically isolated from the system python environment.nisse