[Checkins] SVN: zope.viewlet/trunk/src/zope/viewlet/README.txt
minor typos
Fred L. Drake, Jr.
fdrake at gmail.com
Fri Sep 28 10:32:53 EDT 2007
Log message for revision 80327:
minor typos
Changed:
U zope.viewlet/trunk/src/zope/viewlet/README.txt
-=-
Modified: zope.viewlet/trunk/src/zope/viewlet/README.txt
===================================================================
--- zope.viewlet/trunk/src/zope/viewlet/README.txt 2007-09-28 13:42:37 UTC (rev 80326)
+++ zope.viewlet/trunk/src/zope/viewlet/README.txt 2007-09-28 14:32:52 UTC (rev 80327)
@@ -16,8 +16,8 @@
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 content providers.
+providers are known as viewlets and are only available inside viewlet
+managers, which are just a more complex example of content providers.
Unfortunately, the Java world does not implement this layer separately. The
viewlet manager is most similar to a Java "channel", but we decided against
@@ -25,7 +25,7 @@
has no Java counterpart, since Java does not implement content providers using
a component architecture 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
+implementation less useful 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.
More information about the Checkins
mailing list