[Zope3-checkins] SVN: Zope3/branches/roger-contentprovider/src/zope/viewlet/README.txt Added some explanatory text.

[Stephan Richter]

Log message for revision 39466:
  Added some explanatory text.
  

Changed:
  U   Zope3/branches/roger-contentprovider/src/zope/viewlet/README.txt

-=-
Modified: Zope3/branches/roger-contentprovider/src/zope/viewlet/README.txt
===================================================================
--- Zope3/branches/roger-contentprovider/src/zope/viewlet/README.txt	2005-10-15 12:10:12 UTC (rev 39465)
+++ Zope3/branches/roger-contentprovider/src/zope/viewlet/README.txt	2005-10-15 12:23:15 UTC (rev 39466)
@@ -10,6 +10,27 @@
   >>> from zope.viewlet import interfaces
 
 
+Design Notes
+------------
+
+As mentioned above, besides inserting snippets of HTML at places, we more
+frequently want to define a region in our page and allow specialized content
+providers to be inserted based on configuration. Those specialized content
+providers are known viewlets and are only available inside viewlet managers,
+which are just a more complex example of a content provider.
+
+Unfortunately, the Java world does not implement this layer separately. The
+viewlet manager is most similar to a Java "channel", but we decided against
+using this name, since it is very generic and not very meaningful. The viewlet
+has no Java counterpart, since Java does not implement content providers using
+a component archicture and thus does not register content providers
+specifically for viewlet managers, which I believe makes the Java
+implementation less usefull as a generic concept. In fact, the main design
+goal in the Java world is the implementation of reusable and sharable
+portlets. The scope for Zope 3 is larger, since we want to provide a generic
+framework for building pluggable user interfaces.
+
+
 The Viewlet Manager
 -------------------