[Checkins] SVN: zope.fanstatic/trunk/ Explain the hurry.zoperesource history.

Mon Jan 3 09:03:05 EST 2011

Log message for revision 119311:
  Explain the hurry.zoperesource history.

Changed:
  U   zope.fanstatic/trunk/CHANGES.txt
  U   zope.fanstatic/trunk/src/zope/fanstatic/README.txt

-=-
Modified: zope.fanstatic/trunk/CHANGES.txt
===================================================================

--- zope.fanstatic/trunk/CHANGES.txt	2011-01-03 13:50:58 UTC (rev 119310)
+++ zope.fanstatic/trunk/CHANGES.txt	2011-01-03 14:03:04 UTC (rev 119311)
@@ -1,75 +1,21 @@
 CHANGES
 *******
 
-0.8 (unreleased)
-================
+0.9 (unreleased)
+----------------
 
+Zope.fanstatic version 0.9 is a fundamental rewrite of `hurry.zoperesource`_,
+as a result of the rewrite of `hurry.resource`_ into `fanstatic`_.
+
+Here's a list of essential changes since version 0.7 of hurry.zoperesource:
+
+- Compliance with the Fanstatic API.
+
 - ``++resource++foo/bar/baz.jpg`` expressions in Page Templates are
   still supported by way registering a traversable component for all
-  available resource libraries. There are not zope.browserresource
+  available resource libraries. There are no zope.browserresource
   components involved anymore in zope.fanstatic.
 
-- Full rewrite based on the Fanstatic library (fanstatic.org).
-
-0.7 (2010-10-01)
-================
-
-- Created ResourceDirectories now are registered for ``IBrowserRequest`` the
-  base class of the previously used ``IDefaultBrowserLayer``. So this
-  package can be used when the layer used by the application does not extend
-  ``IDefaultBrowserLayer``, as e. g. `z3c.layer.pagelet` does.
-
-0.6 (2010-07-29)
-================
-
-* Update to work with hurry.resource 0.10 and later. This uses the
-  entry point mechanism to configure any libraries.
-
-  Note that this needs hurry.resource-based packages that themselves
-  have been updated to hurry.resource 0.10's way of defining an entry
-  point and including the resource path in the library. See the
-  `hurry.resource documentation
-  <http://pypi.python.org/pypi/hurry.resource>`_ for more information.
-
-0.5 (2010-07-24)
-================
-
-* Drop the zope.app.component dependency.
-
-* Register the ILibraryUrl adapter for ILibrary instead of Library,
-  to be less specific for the adapter lookup.
-
-* Clearly specify license as ZPL.
-
-0.4 (2009-12-16)
-================
-
-* Updated required packages.
-
-* Use a newer version of hurry.resource which can insert the snippets
-  into HTML itself.
-
-0.3 (2008-12-05)
-================
-
-* ``resource.need()`` needed a request object set up in order to
-  function.  This is rather annoying in tests, which often don't have
-  a request object set up. We now instead return a dummy
-  ``NeededResources`` object in such cases (which will then be thrown
-  away). As a result, it's always safe to call ``resource.need()``
-  during tests, though if no request can be found it will have no
-  effect.
-
-0.2 (2008-10-13)
-================
-
-* Add support for rendering fragments at the bottom of the page. When
-  you call ``hurry.resource.bottom`` resources which are marked bottom-safe
-  will be rendered at the bottom of the web page instead of in the ``<head>``
-  section. When you call ``hurry.resource.bottom(force=True)``, *all*
-  ``.js`` resources will be included at the bottom.
-
-0.1 (2008-10-11)
-================
-
-* Initial public release.
+.. _`hurry.zoperesource`: http://pypi.python.org/pypi/hurry.zoperesource
+.. _`hurry.resource`: http://pypi.python.org/pypi/hurry.resource
+.. _`fanstatic`: http://fanstatic.org

Modified: zope.fanstatic/trunk/src/zope/fanstatic/README.txt
===================================================================
--- zope.fanstatic/trunk/src/zope/fanstatic/README.txt	2011-01-03 13:50:58 UTC (rev 119310)
+++ zope.fanstatic/trunk/src/zope/fanstatic/README.txt	2011-01-03 14:03:04 UTC (rev 119311)
@@ -4,8 +4,7 @@
 This package provides Zope integration for fanstatic. This means
 it's taking care of two things:
 
-* provide access to the needed resources in the WSGI environment
-  throughout the request/response cycle.
+* provide access to the needed resources throughout the request/response cycle.
 
 * provide the base URL for the resources to be rendered.
 

