struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Reddin <gred...@apache.org>
Subject Re: svn commit: r329352 - in /struts/tiles/trunk/xdocs: index.xml navigation.xml
Date Sat, 29 Oct 2005 02:12:00 GMT
This is my first commit.  Anyone care to check it and make sure  
everything is set correctly?

BTW, I noticed the wiki page explained how to set the keywords  
property on xdocs files, but it doesn't say anything about including  
the keywords within the file.  Can someone elaborate on how that is  
supposed to work or is it not a requirement?

Thanks,
Greg

On Oct 28, 2005, at 9:07 PM, greddin@apache.org wrote:

> Author: greddin
> Date: Fri Oct 28 19:07:27 2005
> New Revision: 329352
>
> URL: http://svn.apache.org/viewcvs?rev=329352&view=rev
> Log:
> This begins the process of moving the information from the tiles- 
> documentation web application to the xdocs directory of the tiles  
> subproject.
>
>
> Added:
>     struts/tiles/trunk/xdocs/index.xml   (with props)
> Modified:
>     struts/tiles/trunk/xdocs/navigation.xml
>
> Added: struts/tiles/trunk/xdocs/index.xml
> URL: http://svn.apache.org/viewcvs/struts/tiles/trunk/xdocs/ 
> index.xml?rev=329352&view=auto
> ====================================================================== 
> ========
> --- struts/tiles/trunk/xdocs/index.xml (added)
> +++ struts/tiles/trunk/xdocs/index.xml Fri Oct 28 19:07:27 2005
> @@ -0,0 +1,136 @@
> +<?xml version="1.0"?>
> +<document url="./index.xml">
> +<properties>
> +  <title>The Tiles 1.1 Framework Project</title>
> +</properties>
> +
> +<body>
> +
> +<section name="Welcome To Tiles">
> +    <p>Welcome to the Struts Tiles subproject.  Tiles is a templating
> +    framework.  It can be used to create a common look &amp; feel  
> for a web site or
> +    application and to create reusable view components.  This site  
> will give you
> +    all the information you need to get started.</p>
> +</section>
> +
> +<section name="Tiles Features" href="Features">
> +     <ul>
> +          <li>Screen definitions
> +             <ul>
> +                <li>Create a screen by assembling
> +                   <strong><em>Tiles</em></strong> : header,
footer,
> +                   menu, body, etc.
> +                </li>
> +                <li>
> +                   Definitions can take place :
> +                   <ul>
> +                      <li>in a centralized xml file</li>
> +                      <li>directly in jsp pages</li>
> +                      <li>programatically in struts actions</li>
> +                   </ul>
> +                </li>
> +                <li>
> +                   Definitions provide an inheritance
> +                   mechanism : a definition can extend another one,
> +                   and override parameters.
> +                </li>
> +             </ul>
> +          </li>
> +          <li>
> +             Layouts
> +             <ul>
> +                <li>
> +                   Define common page layouts and reuse
> +                   them across your web site.
> +                </li>
> +                <li>
> +                   Define menu layouts, and use them by
> +                   passing lists of items and links.
> +                </li>
> +                <li>
> +                   Define a portal layout, use it by
> +                   passing a list of <strong><em>Tiles</em></strong>
> +                   (pages) to show.
> +                </li>
> +                <li>
> +                   Reuse existing layouts, or define
> +                   your own.
> +                </li>
> +             </ul>
> +          </li>
> +          <li>
> +             Dynamic page building
> +             <ul>
> +                <li>
> +                   Tiles can be gathered dynamically during
> +                   page reload. It is possible to change any  
> attribute:
> +                   layout, list of Tiles in portal, list of menu
> +                   items, etc.
> +                </li>
> +             </ul>
> +          </li>
> +          <li>
> +             Reuse of <strong><em>Tiles</em></strong> /
> +             Components
> +             <ul>
> +                <li>
> +                   If well defined, a
> +                   <strong><em>Tile</em></strong> can be reused
 
> across multiple
> +                   applications.
> +                </li>
> +                <li>
> +                   Dynamic attributes are used to
> +                   parameterize <em><strong>Tiles</strong></em>.
> +                </li>
> +                <li>
> +                   It is possible to define a library of
> +                   reusable <em><strong>Tiles</strong></em>.
> +                </li>
> +                <li>
> +                   Build a page by assembling predefined
> +                   components, giving them appropriate parameters.
> +                </li>
> +             </ul>
> +          </li>
> +          <li>
> +             Internationalization (i18n)
> +          </li>
> +          <ul>
> +          <li>
> +             It is possible to load different tiles
> +             according to Locale.
> +          </li>
> +          <li>
> +             A mechanism similar to Java properties
> +             files is used for definitions files: you can have one
> +             definition file per Locale. The appropriate  
> definition is
> +             loaded according to the current Locale.
> +          </li>
> +          </ul>
> +          <li>
> +             Multi-channels
> +          </li>
> +          <ul>
> +          <li>
> +             It is possible to load different Tiles
> +             according to a key.
> +          </li>
> +
> +          <li>
> +             For example, the key could be user provilege,
> +             browser type, arbitrary name stored in session, etc.
> +          </li>
> +
> +          <li>
> +             A mechanism similar to Java properties
> +             files is used for definitions files: you can have one
> +             definition file per key. The appropriate definition is
> +             loaded according to the key.
> +          </li>
> +          </ul>
> +       </ul>
> +
> +</section>
> +
> +</body>
> +</document>
>
> Propchange: struts/tiles/trunk/xdocs/index.xml
> ---------------------------------------------------------------------- 
> --------
>     svn:eol-style = native
>
> Propchange: struts/tiles/trunk/xdocs/index.xml
> ---------------------------------------------------------------------- 
> --------
>     svn:keywords = Author Date Id
>
> Modified: struts/tiles/trunk/xdocs/navigation.xml
> URL: http://svn.apache.org/viewcvs/struts/tiles/trunk/xdocs/ 
> navigation.xml?rev=329352&r1=329351&r2=329352&view=diff
> ====================================================================== 
> ========
> --- struts/tiles/trunk/xdocs/navigation.xml (original)
> +++ struts/tiles/trunk/xdocs/navigation.xml Fri Oct 28 19:07:27 2005
> @@ -7,6 +7,7 @@
>    <body>
>
>      <menu name="Tiles">
> +        <item href="index.html" name="Tiles Home"/>
>          <item href="installation.html" name="Installation"/>
>      </menu>
>      <menu name="Taglib Reference">
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message