Grok

==================

* This release happened but never really was fully completed. See the
release notes for 1.0b2 instead.

==================

* Pin grokcore.view to 1.7.

* Import zope.app.container interfaces from their actual definition not from a
re-import.

* JSON views now report a Content-type: text/json. See
https://bugs.launchpad.net/bugs/362902

==================

* Pin grokui.admin to 0.3.2

* Pin grokcore.view to 1.5.

* Pin grokcore.component to 1.6.

==================

* Documentation and doc string updates.

* Pin grokui.admin to 0.3.

* Pin grokcore.view to 1.4.

* Synced versions.cfg with the latest KGS release available at:
http://download.zope.org/zope3.4/3.4.0/versions.cfg

* Expose ``IBeforeTraverseEvent`` for import in the ``grok`` namespace.

==================

See: `upgrade_notes_1.0a1` for special notes on upgrading to this release.

Feature changes
---------------

* Introduced ``grok.interfaces.IGrokSecurityView``, a marker interface
which non-Grok views can use to state that they want to be handled
like regular Grok views by the Grok publisher.

* Expose the ``DirectoryResource`` component from grokcore.view and the
accompanying ``path`` directive.

* Similar to the layers and skins restructuring, the ``grok.RESTProtocol``
baseclass has been removed in favour of a ``grok.restskin(name)`` directive
that can be used on REST layer interfaces. Introduced the IRESTLayer base
interfaces for defining REST layers.

* Besides our extensive existing documentation, we have also started
to add a lot of docstrings to the Grok source code so it becomes
easier to understand.

Bug fixes
---------

* Have GrokForm define an empty actions attribute by default, in order
for "action-less" forms to work easily.

* Allow the grok.layer() directive on JSON components. Closes
https://bugs.launchpad.net/grok/+bug/310558

* Close a bad security hole (also fixed in 0.14.1 and other
releases). See
http://grok.zope.org/blog/security-issue-in-grok-please-upgrade

Restructuring
-------------

* Viewlet-related base classes and helpers have been moved out to a
``grokcore.viewlet`` package which Grok now depends on.

=================

See: `upgrade_notes_0.14` for special notes on upgrading to this release.

Feature changes
---------------

* Grok now officially supports Python 2.5 and still supports Python 2.4.

* Merged the versions from the zope 3.4c7 KGS (known good set):
http://download.zope.org/zope3.4/versions-3.4.0c7.cfg
So we are now using the latest Zope 3 releases for all Zope packages.

Restructuring
-------------

* The ``grok.admin`` subpackage has been factored out to a separate
package ``grokui.admin``. To have the Grok admin UI available in
your environment, add ``grokui.admin`` to the required packages in
the ``setup.py`` of your package.

* Removed ``grok.Skin`` baseclass in favour of a ``grok.skin(name)``
directive that can be used on layer interfaces. Also removed the
``IGrokLayer`` interface in favour of exposing ``IBrowserRequest``
from the grok package.

* Security-related directives and helpers have been moved out to a
``grokcore.security`` package.

* View-related base classes, directives and grokkers have been moved
out to a ``grokcore.view`` package.

* Form-related base classes and helpers have been moved out to a
``grokcore.formlib`` package.

Bug fixes
---------

* Replace zope.deprecation.tests.warn with grok.testing.warn to:

* Make the signature identical to warnings.warn

* To check for \*.pyc and \*.pyo files.

When zope.deprecation is fixed this warn() function can be removed again.
Makes all the tests pass under Python-2.5.