[Checkins] SVN: bluebream/website/docs/v1.0/manual/skinning.rst bit cleanup
Baiju M
baiju.m.mail at gmail.com
Tue Feb 16 13:15:57 EST 2010
Log message for revision 109079:
bit cleanup
Changed:
U bluebream/website/docs/v1.0/manual/skinning.rst
-=-
Modified: bluebream/website/docs/v1.0/manual/skinning.rst
===================================================================
--- bluebream/website/docs/v1.0/manual/skinning.rst 2010-02-16 17:29:43 UTC (rev 109078)
+++ bluebream/website/docs/v1.0/manual/skinning.rst 2010-02-16 18:15:56 UTC (rev 109079)
@@ -18,20 +18,12 @@
widgets, tables etc. Also you will be required to mix and match user
interface components from multiple packages.
-The level of customization of Zope (2 and 3) has been a strong point
-for years. Initially the user interface was customized relying on
-implicit acquisition, where it was simply a matter of adding an
-object higher in the object path to customize the user interface.
-Since implicit acquisition is often hard to debug, the CMF introduced
-the concept of skins, where a skin describes the look and feel of a
-site. Skins could acquire from other skins explicitly.
+In BlueBream, the skin concept is implemented to use the Zope
+component architecture.
-In Zope 3 the concept of skins was reconsidered and re-implemented to
-use the component architecture.
-
There are two terms associated with skinning named, `layer` and
`skin`. Before proceeding, it would be better to understand the
-meaning of these two terms in Zope 3 skinning.
+meaning of these two terms in BlueBream skinning.
Layers
~~~~~~
@@ -43,7 +35,7 @@
* Common artifacts: pages, content providers, viewlet managers, and
viewlets
-* Developed by Zope 3 Python developers
+* Developed by BlueBream (Python) developers
Skins
More information about the checkins
mailing list