Zope Subversion Repository

Zope: zope.security/trunk/src/zope/security/metaconfigure.py

Remove CVS-era Id fossils.

Conform to repository policy.

Added to zope.security the implementation of the simple <module>
directive, so that everyone needing it will no longer have to rely,
for just that reason, upon the monstrous zope.app.security.

Moved the <class> directive implementation from `zope.app.component` to
this package.

Remove unused imports

Remove deprecated zope:content and zope:localUtility directives.

Moving code to satellite.

Wrong deprecation date for the localUtility directive.

Deprecate directive <zope:localUtility>.
Remove deprecated directive <zope:defaultLayer>.

Minor documentation fixes.

Write BBB docstrings for deprecated directives.
These statements should appear within ++apidoc++ for ZCML.

List of deprecated directives:
. zope
	content
	defaultLayer
	defaultView
	factory
	localUtility *not yet deprecated*
	modulealias
	vocabulary

. browser
	layer
	skin
	tool

. renderer
	renderer

Merge of jim-adapter branch:

This branch has three major refactorings on it:

- A redesign of the adapter registration machinery

- A major simplification of local component management

  See zope.component.interfaces.IComponentRegistry.

- A flexible system for combining component registries.

- A beginning of the migration of packages out of zope.app.

- A new package for doing deferred imports.  This allows you
  to make names available at the package level without creating
  circular imports.  See zope.deferredimport and see
  zope.component.__init__ for examples of it's use.  This package
  also provides a way to deprecate names in a module.

- Deprecation of zope. i18nmessageid.MessageID

I should have created checkin messages for individual sets of related
changes, but there were just too many for the time allowed.

Merge philikon-reduce-zcml branch: Implementation of
http://dev.zope.org/Zope3/ReducingTheAmountOfZCMLDirectives.

Massive style cleanup: Move to new raise exception style; for motivation, see:

  http://permalink.gmane.org/gmane.comp.web.zope.zope3/13884

- Removal of Services. You can now access the adapter and utiliy
  registry directly via the site manager's `adapters` and `utilities`
  attribute, respecitvely.

  + Converted Principal Annotation Service to be a utility. Added
    database evolution code to convert all service instances to
    utilities.
  
  + Converted FSSync Service to be a utility.

  + Created the concept of a global site manager. The adapter and
    utility registry, formerly the adapter and utility service, are now
    managed by the site manager.

  + The `zope.app.utility` package has been merged into
    `zope.app.component`. The utility registration class is in
    `site.py`. The utility vocabulary is in `vocabulary.py`.

  + The `zope.app.site` package has been merged into
    `zope.app.component`. The site code can be found in `site.py`.

  + Fixed persistent modules code. Persistent modules are now simply
    utilities providing `IModuleManager`. The local site manager also
    does not know any thing about persistent modules anymore.

  + Updated `zope.app.pluggableauth`, so that it will work as an
    authentication utility.

  + Restructured `zope.app.persentation` (a.k.a page folders) to the new
    component API.

- Simplified the registration framework by only supporting two states:
  active and inactive. This allowed us to get rid of the registration
  stack and the complexity it introduced to the site management.

- Removed all presentation-related APIs from `zope.component`. This
  included the removal of presentation-related interfaces and the
  deprecation of all view-related API functions. One should use the
  adapter API functions instead.

- Implemented some initial deprecation framework, see
  `zope.deprecation`. It allows one to deprecate methods and properties
  in classes as well as any name in a module.

- Moved reusable test setups/APIs from `zope.app.tests` to
  `zope.app.testing`. No reusable testing code should be in a `tests`
  package or module.

Update doc strings to ReST

Removed __metaclass__ and made classes inherit 'object'.

Also made most classic classes new-style classes.

Updated module doc strings where appropriate.

Updated to use ZPL 2.1.

- Created functions to encapsulate the thread-global management of
  sites because we don't actually want to store the site in the thread
  global. We want to store the site manager. Later, there is some
  interesting caching that we can do. We need to encapsulate the site
  management to do this.

- Caused PlacefulSetup to register the site when someone calls
  makeSite. 

- Added an API function, getGlobalService to explicitly get a global
  service.

Tell subversion to expand the Id keyword:
  - replaced old CVS expansion with a clean $Id$
  - set the svn:keywords property to "Id"

When you check-in files in the future and want $Id$ to be expanded,
make sure it reads "$Id$" in that file; then set svn:keywords to "Id".

Set mime-type or svn-eol property from cvs expansion data

Removed the permission attribute from the two factoy directives. All factories
are public now. This was discussed recently on the mailing list and Jim okayed
it.

Adjusted code to use the new APIs for permissions and principals. Also, use
the utility service instead of the permission registry to look up permissions.

Renamed interface methods:

isImplementedByInstancesOf to implementedBy
  isImplementedBy            to providedBy

removed local interface service stuff, it uses global utility service.

Remove unused imports.

Added factory 'info' to the factory service. This can be used to lookup
title and description for registered factories. Prior to this change, factory
title and description defined in ZCML was discarded.

This change is per an exchange back in May:

http://mail.zope.org/pipermail/zope3-dev/2003-May/006915.html

Note that only the factory info portion of the proposed change is
implemented in this commit. The ability to enumerate registered factories
was implemented earlier.

Changed the way factory permissions are handled. Now just create a
checker to be used later when the factory is proxied. Don't proxy the
factory right away.

Removed unused imports.

Merging dreamcatcher's TTW Schema branch:

1. Fixed Bug in adding that would cause infinite loops when the menu items
   action was not a valif view or factory id.

2. Extended adding to support more complex views. Until now we only
   supported constructions like "+/AddView=id". Now you are able to say
   "+/AddView/More=id", which means that more information can be carried
   in the URL. This can be used in many ways, including multi-page adding
   wizards. In my case I needed it to pass in the type of the TTW Schema-
   based Content Component.

3. Added Local Menus. This was a pain in the butt, but I think I got a
   fairly nice model, where you can create local Menu Services, and Menus
   are simply named utilities. When active they are menus in the menu
   service. This is very similar to the local interface service and TTW
   Schema.

4. Made some modifications to TTW Schema, cleaned up the code and moved
   the browser code and interfaces to the places they belong.

5. Added a Content Component Definition utility component, which takes a
   Schema and creates a content component for it, including permission
   settings and a menu entry. Currently the menu entry is always made to
   a local 'add_content' menu. I will change this and make it actually a
   screen, where the menu and title of the menu item can be chosen by the
   developer. Mmmh, should I add a factory for the definition as well, so
   that the content component is also available via python?

6. Added a Content Component Instance component that represents an
   instance od a Content Component Definition. You will never directly
   encounter this component, since it is automatically used by the adding
   code of the Content Component Definition.

7. Cleanups by both dreamcatcher and myself.

That's it. For more details see the branch checkin messages. I now consider
the dreamcatcher-ttwschema-branch closed.

Reasonably big batch of changes. Added methods to query factories by interface. Added tests for them. Registered all fields from zope.schema as factories. Added basic tests for that. Made the contentdirective use a dottedname instead of a class as the id when an id is not provided. Cleanspace Whitening here and there.

Actually use title and description in factories. Also some whitespace here and there

Here we go again. All tests have been run twice and passed. Sorry again for
the trouble I've caused. Anthony and Steve, I owe you guys are beer.

Converted the three most important packages that define ZCML directives
to the new ZCML architecture (using schemas):

- zope.app.component

- zope.app.browser.form

- zope.app.publisher.browser

Backing out philiKON's changes - they broke the functional tests, and
from his signoff on IRC, I don't think he's going to be around until
Monday. As I'm working on the Catalog functional tests, this is pretty
annoying. I tried to figure out how to just back out bits til I found the
broken stuff, but it's a pretty serious refactoring. I'll send a message
to zope3-checkins with the CVS commands used for this, so that someone
can undo the backout if they wish.

Converted the three most important packages that define ZCML directives
to the new ZCML architecture (using schemas):

- zope.app.component

- zope.app.browser

- zope.app.publisher.browser

No longer declare INonEmptyDirective and ISubdirectiveHandler.
Complex directive handlers and now recognized through the meta
configuration.

updated to use new-style interface declarations

Moved  zope.app.contentdirective into zope.app.component.

	Diffs between and
	Generate output suitable for use with a patch program
	Type of Diff should be a Colored Diff Long Colored Diff Unidiff Context Diff Side by Side

---

Sort log by: Not sorted Commit date Revision

---

webmaster@zope.org Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help