[Zope-Checkins] SVN: Products.Five/trunk/ - prepared Five trunk for
being moved to Zope core
Yvo Schubbe
y.2007- at wcm-solutions.de
Mon Jan 8 10:26:52 EST 2007
Log message for revision 71810:
- prepared Five trunk for being moved to Zope core
Changed:
U Products.Five/trunk/CHANGES.txt
U Products.Five/trunk/CREDITS.txt
D Products.Five/trunk/INSTALL.txt
U Products.Five/trunk/README.txt
D Products.Five/trunk/doc/ZopePublicLicense.txt
D Products.Five/trunk/doc/five14goals.txt
U Products.Five/trunk/formlib/configure.zcml
U Products.Five/trunk/version.txt
-=-
Modified: Products.Five/trunk/CHANGES.txt
===================================================================
--- Products.Five/trunk/CHANGES.txt 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/CHANGES.txt 2007-01-08 15:26:52 UTC (rev 71810)
@@ -2,29 +2,9 @@
Five Changes
============
-Five 1.6 (unreleased)
-=====================
+This change log is discontinued. For changes after Five 1.5.1 see Zope's main
+CHANGES.txt file.
-Bugfixes
---------
-
-* View methods which aren't explicitly declared as allowed must be marked
- private explicitly to avoid being web publishable.
-
-* Port code from Zope 3 making resource directories recursive.
- Thanks to Richard Waid.
-
-
-* site/metaconfigure: Local site hook now only applied once per class, so
- multiple <five:localsite> tags for the same class won't cause config
- errors.
-
-Five 1.5.2 (unreleased)
-=======================
-
-* i18n: Synced FiveTranslationService implementation with Zope 3.3. This makes
- sure that the TestMessageFallbackDomain is used if registered.
-
Five 1.5.1 (2006-11-04)
=======================
Modified: Products.Five/trunk/CREDITS.txt
===================================================================
--- Products.Five/trunk/CREDITS.txt 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/CREDITS.txt 2007-01-08 15:26:52 UTC (rev 71810)
@@ -27,7 +27,7 @@
- Dieter Maurer (dieter at handshake.de)
-- Yvo Schubbe (y.2005- at wcm-solutions.de)
+- Yvo Schubbe (y.2007- at wcm-solutions.de)
- Malcolm Cleaton (malcolm at jamkit.com)
Deleted: Products.Five/trunk/INSTALL.txt
===================================================================
--- Products.Five/trunk/INSTALL.txt 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/INSTALL.txt 2007-01-08 15:26:52 UTC (rev 71810)
@@ -1,38 +0,0 @@
-How to install Five
-===================
-
-Requirements for Five 1.5
--------------------------
-
-* Zope 2.10 with Python 2.4.1+
-
-Note that Five 1.5 is already part of Zope 2.10. You can still
-install a newer Five version in your instance, if you like. It will
-override the Five product inside the Zope tree.
-
-
-Compatability matrix
---------------------
-
-The following table shows which Five version can and should be used
-with which Zope 2 and Zope 3 versions.
-
-============ =========== ======== =========
-. Zope 2.8 Zope 2.9 Zope 2.10
------------- ----------- -------- ---------
-. Zope X3 3.0 Zope 3.2 Zope 3.3
-============ =========== ======== =========
-Five 1.0 included
-Five 1.2 X
-Five 1.3 included
-Five 1.4 X
-Five 1.5 included
-Five trunk X
-============ =========== ======== =========
-
-
-Running the tests
------------------
-
-For information on how to install the automatic Five tests, please see
-``tests/README.txt``.
Modified: Products.Five/trunk/README.txt
===================================================================
--- Products.Five/trunk/README.txt 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/README.txt 2007-01-08 15:26:52 UTC (rev 71810)
@@ -38,15 +38,8 @@
* Content Providers and Viewlets
-Together with another product, CMFonFive, Five can integrate into CMF.
-
For more information, see ``doc/features.txt``.
-How to install Five
--------------------
-
-See ``INSTALL.txt``.
-
How to use Five
---------------
Deleted: Products.Five/trunk/doc/ZopePublicLicense.txt
===================================================================
--- Products.Five/trunk/doc/ZopePublicLicense.txt 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/doc/ZopePublicLicense.txt 2007-01-08 15:26:52 UTC (rev 71810)
@@ -1,54 +0,0 @@
-Zope Public License (ZPL) Version 2.1
--------------------------------------
-
-A copyright notice accompanies this license document that
-identifies the copyright holders.
-
-This license has been certified as open source. It has also
-been designated as GPL compatible by the Free Software
-Foundation (FSF).
-
-Redistribution and use in source and binary forms, with or
-without modification, are permitted provided that the
-following conditions are met:
-
-1. Redistributions in source code must retain the
- accompanying copyright notice, this list of conditions,
- and the following disclaimer.
-
-2. Redistributions in binary form must reproduce the accompanying
- copyright notice, this list of conditions, and the
- following disclaimer in the documentation and/or other
- materials provided with the distribution.
-
-3. Names of the copyright holders must not be used to
- endorse or promote products derived from this software
- without prior written permission from the copyright
- holders.
-
-4. The right to distribute this software or to use it for
- any purpose does not give you the right to use
- Servicemarks (sm) or Trademarks (tm) of the copyright
- holders. Use of them is covered by separate agreement
- with the copyright holders.
-
-5. If any files are modified, you must cause the modified
- files to carry prominent notices stating that you changed
- the files and the date of any change.
-
-Disclaimer
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS''
- AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
- NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
- AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
- NO EVENT SHALL THE COPYRIGHT HOLDERS BE
- LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
- EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
- LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
- CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
- OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
- SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
- DAMAGE.
Deleted: Products.Five/trunk/doc/five14goals.txt
===================================================================
--- Products.Five/trunk/doc/five14goals.txt 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/doc/five14goals.txt 2007-01-08 15:26:52 UTC (rev 71810)
@@ -1,107 +0,0 @@
-===============================
-Porting Five to Zope 3.1+ notes
-===============================
-
-Introduction
-------------
-
-Five needs to work in Zope 2.9. Zope 2.9 will ship with Zope 3.2. This
-means Five will need to work with Zope 3.2. Since Zope 3.2 doesn't
-truly exist yet we'll target Zope 3.1 for now.
-
-A Five Roadmap
---------------
-
-Here is a tentative Five roadmap:
-
-Five 1.1 is to be released shortly, and its main feature is a
-refactored directory structure and Zope 3 i18n for Zope 2. It's still
-targeting the Zope X3.0 that's in Zope 2.8.
-
-Five 1.2 is still targetting Zope 2.8, and its main expected feature
-is support for local utilities.
-
-Five 1.3 is targetting Zope 2.9 and thus Zope 3.2. We're talking about
-this release of Five in this document.
-
-Main problem
-------------
-
-Zope 3.1 has internal changes that Five needs to support. Five works
-by reimplementing ZCML statements it supplies in the context of Zope
-2. This reimplementation is hard to maintain, as for each Zope 3
-upgrade we need to review all these ZCML statements and port them into
-Five again.
-
-The straightforward way to start supporting Zope 3.1+ with Five would
-be to review all the ZCML statements in Five and update them to work
-with Zope 3.1+.
-
-A more ambitious but nicer solution would be if we could reuse the
-Zope 3 ZCML statements directly. If we could accomplish this,
-maintainability of Five would be improved by a lot. Far less review of
-Five would be necessary for each Zope 3 upgrade. In the rest of this
-document we'll be discussing this scenario.
-
-Reasons for Five's modified ZCML statements
--------------------------------------------
-
-Five ships with modified implementations of Zope 3 ZCML statements for
-a number of reasons:
-
-* could not use new-style classes that are in Zope 3 due to
- ExtensionClass.
-
-* Five views need to work with the Zope 2 publisher, and this expects
- different things than the Zope 3 publisher.
-
-* cannot use the Zope 3 security system, while the Zope 3 ZCML calls
- into this to configure it.
-
-* Five views need to work with the Zope 2 security system. This means
- Five needs to issue Zope 2 style security declarations for views.
-
-We'll go into more detail about each of these points below.
-
-New-style ExtensionClass
-========================
-
-Five needed to be compatible with Zope 2.7, which uses old-style
-ExtensionClass. This made life difficult for Five, as Zope 3 uses
-new-style Python classes in many places. It's not easy to mix the two.
-
-Zope 2.8 changed to allow new-style ExtensionClasses, which are
-compatible with new-style Python classes. This means Five can
-hopefully be simplified as we can forget about old-style
-ExtensionClasses.
-
-Five views need to work with the Zope 2 publisher
-=================================================
-
-The Zope 2 publisher expects something quite different than the Zope 3
-publisher.
-
-* does what is returned to the publisher need to inherit from
- Acquisition.Explicit? (security reasons?)
-
-* we may need something that calls the right methods on the Zope 3
- view (such as browserDefault, __call__ and publishTraverse)
-
-Cannot use the Zope 3 security system
-=====================================
-
-Do the Zope 3 security calls get in the way? Five currently removes
-these calls, but perhaps doing the calls does not harm.
-
-If they do interface, we could perhaps still trick things into
-working harmlessly.
-
-Five must issue Zope 2 security declarations for views
-======================================================
-
-This cannot be done by the ZCML implementation of Zope 3. We could
-hopefully do this by following the following pattern::
-
- def our_directive_implementation(...):
- original_directive_implementation(...)
- do_the_zope2_work(...)
Modified: Products.Five/trunk/formlib/configure.zcml
===================================================================
--- Products.Five/trunk/formlib/configure.zcml 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/formlib/configure.zcml 2007-01-08 15:26:52 UTC (rev 71810)
@@ -10,6 +10,8 @@
<!-- Error view for 'Invalid' -->
<adapter
+ for="zope.interface.Invalid
+ zope.publisher.interfaces.browser.IBrowserRequest"
factory=".errors.InvalidErrorView"
permission="zope.Public"
/>
Modified: Products.Five/trunk/version.txt
===================================================================
--- Products.Five/trunk/version.txt 2007-01-08 14:44:01 UTC (rev 71809)
+++ Products.Five/trunk/version.txt 2007-01-08 15:26:52 UTC (rev 71810)
@@ -1 +1 @@
-Five 1.5
+Five 1.5.1+
More information about the Zope-Checkins
mailing list