[Checkins] SVN: bluebream/website/docs/v1.0/manual/ bit cleanup

[Baiju M]

Log message for revision 110111:
  bit cleanup
  

Changed:
  U   bluebream/website/docs/v1.0/manual/browserpage.rst
  U   bluebream/website/docs/v1.0/manual/skinning.rst

-=-
Modified: bluebream/website/docs/v1.0/manual/browserpage.rst
===================================================================
--- bluebream/website/docs/v1.0/manual/browserpage.rst	2010-03-22 15:53:02 UTC (rev 110110)
+++ bluebream/website/docs/v1.0/manual/browserpage.rst	2010-03-23 03:40:17 UTC (rev 110111)
@@ -23,11 +23,11 @@
 
   Hello, World !
 
-Here is how to register a page for IFolder interface::
+Here is how to register a page for ``IFolder`` interface::
 
   <browser:page
     name="helloworld.html"
-    for="zope.app.folder.interfaces.IFolder"
+    for="zope.site.interfaces.IFolder"
     template="helloworld.pt"
     permission="zope.Public"
     /> 
@@ -47,20 +47,19 @@
 Implementation
 ~~~~~~~~~~~~~~
 
-Normally view components are added inside `browser` package inside
-your main package.  The organization of the browser code is really up
-to you and the above examples are just the most basic rules of thumb.
+The organization of the browser code is really up to you and the above
+examples are just the most basic rules of thumb.
 
-Here is simple view defined::
+Here is a simple view defined::
 
-  from zope.publisher.browser import BrowserPage
-  from zope.app.folder import interfaces
+  from zope.formlib import DisplayForm
+  from zope.site.interfaces import IFolder
 
-  class HelloWorld(BrowserPage):
+  class HelloWorld(DisplayForm):
 
       def subFolderIds(self):
           for name, subobj in self.context.items():
-              if interfaces.IFolder.providedBy(subobj):
+              if IFolder.providedBy(subobj):
                   yield name 
 
 Since methods and attributes of the view component are directly used

Modified: bluebream/website/docs/v1.0/manual/skinning.rst
===================================================================
--- bluebream/website/docs/v1.0/manual/skinning.rst	2010-03-22 15:53:02 UTC (rev 110110)
+++ bluebream/website/docs/v1.0/manual/skinning.rst	2010-03-23 03:40:17 UTC (rev 110111)
@@ -23,7 +23,8 @@
 
 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 BlueBream skinning.
+meaning of these two terms in BlueBream skinning.  Skins are directly
+provided by a request
 
 Layers
 ~~~~~~
@@ -69,34 +70,12 @@
 component lookup techniques.  This book will discuss this in more
 detail later.
 
-Skins are directly provided by a request
-
-
-Core skins
-----------
-
-* Access skin using ++skin++Name after the server root
-
-* Core Skins that are part of the repository
-
-  - Rotterdam -- the default skin shown
-
-  - Boston -- a newer skin featuring viewlets
-
-  - Basic -- a skin with no layout styles
-
-  - Debug -- based on Rotterdam, shows debug information upon
-    failures
-
-* Try http://localhost:8080/++skin++Boston
-
 Unfortunately, it is hard to reuse the UI components developed for
 these skins, since they still rely on the not so flexible macro
 pattern.  Thus, it is better if you start from scratch.  This will
 also avoid a lot of the overhead that comes with the over-generalized
 core skins.
 
-
 A new skin
 ----------
 
@@ -173,17 +152,9 @@
 ~~~~~~~~~~~~~~~~~
 
 Skins are technically interfaces defined using ``zope.interface``
-package.  To create a custom skin it is always better to inherit from
-a standard layer or another skin interface.  It is by convention that
-skins will be created in sub-package named ``skin`` in your
-``browser`` package of your main package.  For example, if your
-package name is ``foo``, then ``foo.browser.skin`` will be the skin
-package, but this is not mandatory.  Your skin interfaces can be
-defined in ``foo.browser.skin.interfaces``.
+package.  Write an interface for each new skin that inherits the Hello
+World application layer::
 
-Write an interface for each new skin that inherits the Hello World
-application layer::
-
   class IBasicSkin(IHelloWorldLayer):
       """Basic Skin for Hello World App."""