Author: bdaw Date: 2007-05-02 17:35:51 -0400 (Wed, 02 May 2007) New Revision: 7178 Added: docs/trunk/referenceGuide/en/images/content/cms.png docs/trunk/referenceGuide/en/images/content/fs1.png docs/trunk/referenceGuide/en/images/content/fs2.png docs/trunk/referenceGuide/en/images/content/fs3.png Modified: docs/trunk/referenceGuide/en/modules/contentIntegration.xml Log: - few images in contentintegration chapter Added: docs/trunk/referenceGuide/en/images/content/cms.png =================================================================== (Binary files differ) Property changes on: docs/trunk/referenceGuide/en/images/content/cms.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: docs/trunk/referenceGuide/en/images/content/fs1.png =================================================================== (Binary files differ) Property changes on: docs/trunk/referenceGuide/en/images/content/fs1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: docs/trunk/referenceGuide/en/images/content/fs2.png =================================================================== (Binary files differ) Property changes on: docs/trunk/referenceGuide/en/images/content/fs2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: docs/trunk/referenceGuide/en/images/content/fs3.png =================================================================== (Binary files differ) Property changes on: docs/trunk/referenceGuide/en/images/content/fs3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: docs/trunk/referenceGuide/en/modules/contentIntegration.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/contentIntegration.xml 2007-05-02 19:12:02 UTC (rev 7177) +++ docs/trunk/referenceGuide/en/modules/contentIntegration.xml 2007-05-02 21:35:51 UTC (rev 7178) @@ -65,6 +65,10 @@ <emphasis>edit_content</emphasis> has been introduced. It signals to the portlet that it is editing the content portion of the state of a portlet. The traditional edit mode is not used because the edit mode is more targetted to configure how the portlet show content to the end user rather than what content it shows.</para> + <imageobject> + <imagedata align="center" fileref="images/content/cms.png" format="png"/> + </imageobject> + <caption>Example of content customization - CMS Portlet</caption> </sect1> <sect1> <title>Content Driven Portlet</title> @@ -207,7 +211,11 @@ <sect3> <title>The editor</title> <para>The editor is probably the longest part of the portlet. It tries to stay simple though and goes directly - to the point.</para> + to the point.</para> + <imageobject> + <imagedata align="center" fileref="images/content/fs1.png" format="png"/> + </imageobject> + <caption>Content editor of FSContentDrivenPortlet in action</caption> <programlisting><![CDATA[ protected void doEditContent(RenderRequest req, RenderResponse resp) throws PortletException, PortletSecurityException, IOException @@ -341,6 +349,10 @@ </sect3> <sect3> <title>Hooking the portlet into the portal</title> + <imageobject> + <imagedata align="center" fileref="images/content/fs2.png" format="png"/> + </imageobject> + <caption>Management portlet with <emphasis>filesystem</emphasis> content type enabled</caption> <para>Finally we need to make the portal aware of the fact that the portlet can edit and interpret content. For that we need a few descriptors. The <emphasis>portlet.xml</emphasis> descriptor will define our portlet, the <emphasis>portlet-instances.xml</emphasis> will create a single instance of our portlet. The @@ -425,6 +437,10 @@ <height>1</height> </window> ]]></programlisting> + <imageobject> + <imagedata align="center" fileref="images/content/fs3.png" format="png"/> + </imageobject> + <caption>Final effect - portal window with FSContentDrivenPortlet</caption> <note>How to configure CMS file this way is covered in the CMS chapter: <xref linkend="configuration-cms_content"/></note> </sect1> </chapter>