[Checkins] [zopefoundation/zope.app.basicskin] 5ce6a7: Convert skins and layers that didn't have interfac...

[GitHub]

  Branch: refs/heads/monolithic-zope3-philikon-simplify-skinning
  Home:   https://github.com/zopefoundation/zope.app.basicskin
  Commit: 5ce6a791023958ca56b7ceea3136e19dd727831b
      https://github.com/zopefoundation/zope.app.basicskin/commit/5ce6a791023958ca56b7ceea3136e19dd727831b
  Author: Philipp von Weitershausen <philipp at weitershausen.de>
  Date:   2006-02-19 (Sun, 19 Feb 2006)

  Changed paths:
    A __init__.py
    A configure.zcml

  Log Message:
  -----------
  Convert skins and layers that didn't have interface equivalents yet to the new
system.


  Commit: 7d3fb5001ac959411f33148761981562dd609c92
      https://github.com/zopefoundation/zope.app.basicskin/commit/7d3fb5001ac959411f33148761981562dd609c92
  Author: Philipp von Weitershausen <philipp at weitershausen.de>
  Date:   2006-02-19 (Sun, 19 Feb 2006)

  Changed paths:
    M __init__.py

  Log Message:
  -----------
  * Make zope.app.layers and zope.app.skins a proper module (even though
  they're going to go away). Why they had to be created from Python
  is beyond me, or why they had to be created in the first place.

* Introduce a hook to zope.app.layers and zope.app.skins that lets skins
  and layers register themselves there.  We need this for BBB compat
  when we're using <interface /> now instead of <browser:skin />.
  Accessing the skins and layers through those modules will trigger a 
  deprecation warning.

* Add a BBB awareness parameter to the browser:layer directive that let's
  us continue to use it until its removed without issuing a deprecation
  warning.  We need to continue to use it for BBB reasons (because some
  code might be looking up layers by getting the ILayer utilities, for
  example).


Compare: https://github.com/zopefoundation/zope.app.basicskin/compare/5ce6a7910239^...7d3fb5001ac9