[Checkins] SVN: zopetoolkit/branches/ccomb/ Update readme, avoid duplicated information between readme and the publicly visible index.rst

[Hanno Schlichting]

Log message for revision 113865:
  Update readme, avoid duplicated information between readme and the publicly visible index.rst
  

Changed:
  U   zopetoolkit/branches/ccomb/README.txt
  U   zopetoolkit/branches/ccomb/index.rst

-=-
Modified: zopetoolkit/branches/ccomb/README.txt
===================================================================
--- zopetoolkit/branches/ccomb/README.txt	2010-06-26 09:06:00 UTC (rev 113864)
+++ zopetoolkit/branches/ccomb/README.txt	2010-06-26 09:21:27 UTC (rev 113865)
@@ -10,8 +10,8 @@
 packages which are under review for inclusion.
 
 Also, specific versions have been tested together (including their
-dependencies) and can directly be used with a buildout by specifying this file
-via the ``extends`` mechanism.
+dependencies) and can directly be used with a buildout by specifying the
+``ztk-versions.cfg`` file via the ``extends`` mechanism.
 
 To test the ZTK, run ``bin/test-ztk``.
 
@@ -23,43 +23,11 @@
 Transition support
 ------------------
 
-The libraries now maintained in the Zope Toolkit were previously
-organized differently. Much code now maintained as part of the Zope
-Toolkit was originally part of a set of packages in the ``zope.app.``
-namespace. This code could in the past only be used by importing from
-``zope.app.*`` packages, but has since been extracted into ``zope.*``
-libraries to make it more reusable, and to leave old largely unused
-code behind in ``zope.app.*``.
+For a limited period of time, we maintain a second set of versions in the
+``zopeapp.cfg`` set. This transition support should help existing applications
+to move to the Zope Toolkit. You can extend from the ``zopeapp-versions.cfg``
+via the buildout extends mechanism.
 
-If you are a developer of an application or a framework that makes use
-of the libraries now maintained within the Zope Toolkit, you need a
-way to transition your code to the Zope Toolkit. The first step would
-be to use ``ztk.cfg``, but you likely still have imports to
-``zope.app.*`` that you need to update. The ``zopeapp.cfg`` file allows
-you to build and test your application during this conversion process.
+To test the Zope App set, run ``bin/test-zopeapp``.
 
-The ``zopeapp.cfg`` package set is equivalent to the core ``ztk.cfg`` set,
-in that it offers a controlled set of ZTK compatible ``zope.app.*`` packages.
-To help you transition your code, you can update your ``buildout.cfg`` to
-extend both ``ztk.cfg`` and ``zopeapp.cfg``.
-
-After doing this, we highly recommend you to change your code's
-imports from ``zope.app.*`` to the new places in ``zope.*``
-wherever possible. The package's changelogs should contain information
-as to where things are moved.  If not, try inspecting the module you
-are importing from - the equivalent imports to ``zope.*`` are likely
-there.
-
-It may be that you are not able to change all your imports to ``zope.*``.
-We would like to hear from you where this is not possible. We are
-deliberately leaving old UI code behind in ``zope.app.*``, but it may be
-we need to extract some more code into a more reusable form.
-
-The transition support and ``zope.app.*`` support is limited: the zopeapp
-legacy support will be officially retired from the ZTK after january
-1, 2011.
-
-Unless maintainers step up for some of these packages, compatibility updates
-for most of these packages will also likely end. You are of course still
-free to use older versions, but we highly recommend you upgrade your code to
-the ZTK to receive the benefits of our continued maintenance efforts.
+For more details read the ZTK 1.0 release notes.

Modified: zopetoolkit/branches/ccomb/index.rst
===================================================================
--- zopetoolkit/branches/ccomb/index.rst	2010-06-26 09:06:00 UTC (rev 113864)
+++ zopetoolkit/branches/ccomb/index.rst	2010-06-26 09:21:27 UTC (rev 113865)
@@ -33,9 +33,12 @@
 indirect dependencies; if you see an import error this is probably the
 case.
 
-We recommend you update your existing code to import from the new
-packages if possible. We list major changes below.
+We recommend you update your existing code to import from the new packages if
+possible. The transition support and ``zope.app.*`` support is limited: the
+legacy support will be officially retired from the ZTK after January 1,
+2011.
 
+
 Migration issues
 ----------------