On Thursday 05 January 2006 08:28, Jean-Marc Orliaguet wrote: > PS: note that "viewlets" are known outside the Zope3 world as being > small tutorial movies: > http://psptips.com/6/viewlets/ > http://www.pmwdc.com/skies/ > http://www.geek.com/tipstrix/qarbon/ > http://www.djdenham.com/Basic_Windows.htm > http://www.datacad.com/support/bulletin/Viewlets/viewlets.htm
Viewlets in our case are a wordplay on the term "view", because they are sub-views or view fragments. In any case, the meaning of viewlets in both settings is very different and thus hard to confuse. > I wonder why "portlets" are called "viewlets" in Zope3. Because viewlets do not fulfill all the requirements of a portlet. Portlets have to provide very specific user interactions, which viewlets do not promise. For example, portlets must be able to be minimized, selectively be removed, be fully self-contained and sharable across servers. The reason we should not use the term portlet lightly is because we are working in the same industry, Content Management. People from the Java world have (rightfully) very specific expectations of portlets. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training _______________________________________________ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
