Author: dsvyatobatsko Date: 2008-03-20 13:28:45 -0400 (Thu, 20 Mar 2008) New Revision: 7024 Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/treeNodesAdaptor/usage.xhtml Log: [RF-2626] Demo site: corrections of Recursive Tree Adaptor and Tree Adaptor demo layouts Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/treeNodesAdaptor/usage.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/treeNodesAdaptor/usage.xhtml 2008-03-20 17:28:01 UTC (rev 7023) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/treeNodesAdaptor/usage.xhtml 2008-03-20 17:28:45 UTC (rev 7024) @@ -20,6 +20,9 @@ the second "nodes" is used on another recursion levels (the second level and deeper). </p> + <fieldset class="demo_fieldset"> + <legend class="demo_legend">Example</legend> + <h:panelGroup rendered="#{not empty fileSystemBean.sourceRoots}"> <div class="sample-container" > <ui:include src="/richfaces/treeNodesAdaptor/examples/recursiveAdaptor.xhtml"/> @@ -52,16 +55,19 @@ The information for this demo is generated and incorporated in the richfaces-demo.war file with Maven process. Demo artifacts are located under /WEB-INF/src folder.<br/> As soon as you read this text, you have no such folder in your run-time enviroment - right now.<br /> + right now.<br/> If you use Jetty to run, use 'mvn jetty:run-war' command. </f:verbatim> - + </fieldset><br/><br/> <p>Model adaptor components can be nested without any limitations. The following code-snippet shows an example of using Nodes Adapter along with rich:tree</p> - <div class="sample-container"> - <rich:insert src="/richfaces/treeNodesAdaptor/snippets/sample.xhtml" highlight="xhtml" /> - </div> - + <fieldset class="demo_fieldset"> + <legend class="demo_legend">Code</legend> + + <div class="sample-container"> + <rich:insert src="/richfaces/treeNodesAdaptor/snippets/sample.xhtml" highlight="xhtml" /> + </div> + </fieldset> <p>Data model nodes are wired to treeNode components by nesting treeNode components with a "type" attribute not defined inside model adaptor components. The first rendered one is used, or the default one if all treeNode components are non-rendered.