commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@apache.org
Subject cvs commit: jakarta-commons/jelly/xdocs pipeline.xml jellyswing.xml overview.xml todo.xml faq.xml jellyunit.xml gettingstarted.xml jellyswt.xml
Date Wed, 08 Sep 2004 05:40:45 GMT
dion        2004/09/07 22:40:45

  Modified:    jelly/xdocs pipeline.xml jellyswing.xml overview.xml
                        todo.xml faq.xml jellyunit.xml gettingstarted.xml
                        jellyswt.xml
  Log:
  detab
  
  Revision  Changes    Path
  1.4       +34 -34    jakarta-commons/jelly/xdocs/pipeline.xml
  
  Index: pipeline.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/pipeline.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- pipeline.xml	25 Feb 2004 01:10:23 -0000	1.3
  +++ pipeline.xml	8 Sep 2004 05:40:45 -0000	1.4
  @@ -48,7 +48,7 @@
   </p>
   
   </subsection>
  -	
  +    
   <subsection name="Using Tags as source, filter, transformation or destination in a pipeline">
   
   <p>
  @@ -65,22 +65,22 @@
   </p>
   
   <ul>
  -	<li>
  -		optionally evaluate its body based on some condition
  -	</li>
  -	<li>
  -		loop over its body via some iteration
  -	</li>
  -	<li>
  -		parse its body into some DOM model or turn the XML events into some kind of Java objects

  -		or other kind of data structure
  -	</li>
  -	<li>
  -		perform some arbitrary XML event transformation, like XSLT or apply some SAX Filter etc.
  -	</li>
  -	<li>
  -		output the XML events to some destination
  -	</li>
  +    <li>
  +        optionally evaluate its body based on some condition
  +    </li>
  +    <li>
  +        loop over its body via some iteration
  +    </li>
  +    <li>
  +        parse its body into some DOM model or turn the XML events into some kind of Java
objects 
  +        or other kind of data structure
  +    </li>
  +    <li>
  +        perform some arbitrary XML event transformation, like XSLT or apply some SAX Filter
etc.
  +    </li>
  +    <li>
  +        output the XML events to some destination
  +    </li>
   </ul>
   
   <p>
  @@ -90,22 +90,22 @@
   </p>
   
   <ul>
  -	<li>
  -		parsing XML, transforming it with XSLT or using XPath via the <a href="libs/xml/tags.html">xml</a>
library
  -	</li>
  -	<li>
  -		parsing HTML via the <a href="libs/html/tags.html">html</a> library
  -	</li>
  -	<li>
  -		performing XML validation against DTD, XML Schema or RelaxNG using the <a href="libs/validate/tags.html">validate</a>
library
  -	</li>
  -	<li>
  -		performing SOAP operations via Apache Axis with the <a href="libs/soap/tags.html">soap</a>
library
  -	</li>
  -	<li>
  -		mixing and matching the processing of XML in pipelines with support for other libraries
like 
  -		Ant, SQL, HTTP, JMS etc.
  -	</li>
  +    <li>
  +        parsing XML, transforming it with XSLT or using XPath via the <a href="libs/xml/tags.html">xml</a>
library
  +    </li>
  +    <li>
  +        parsing HTML via the <a href="libs/html/tags.html">html</a> library
  +    </li>
  +    <li>
  +        performing XML validation against DTD, XML Schema or RelaxNG using the <a href="libs/validate/tags.html">validate</a>
library
  +    </li>
  +    <li>
  +        performing SOAP operations via Apache Axis with the <a href="libs/soap/tags.html">soap</a>
library
  +    </li>
  +    <li>
  +        mixing and matching the processing of XML in pipelines with support for other libraries
like 
  +        Ant, SQL, HTTP, JMS etc.
  +    </li>
   </ul>
   
   <p>
  @@ -124,7 +124,7 @@
           </soap:invoke>
         </x:transform>
       </j:file>
  -  </j:if>		
  +  </j:if>        
   ]]>
   </source>
   
  
  
  
  1.6       +2 -2      jakarta-commons/jelly/xdocs/jellyswing.xml
  
  Index: jellyswing.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/jellyswing.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- jellyswing.xml	1 Sep 2004 05:41:35 -0000	1.5
  +++ jellyswing.xml	8 Sep 2004 05:40:45 -0000	1.6
  @@ -44,7 +44,7 @@
           appear with pull down menus, a splitter pane, a form, entry fields, buttons and
a table.
         </p>
         <source>
  -	maven demo:swing
  +    maven demo:swing
         </source>
         <p>
           This example even shows that simple actions can be coded in Jelly script too! Though
typically most
  @@ -65,7 +65,7 @@
           <code>jelly-tags/swing</code> directory.
         </p>
         <source>
  -	maven jelly:runner
  +    maven jelly:runner
         </source>
         <p>
           This makes developing Jelly scripts and JellySwing scripts in particular, much
more RAD-like.
  
  
  
  1.12      +18 -18    jakarta-commons/jelly/xdocs/overview.xml
  
  Index: overview.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/overview.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- overview.xml	25 Feb 2004 01:10:23 -0000	1.11
  +++ overview.xml	8 Sep 2004 05:40:45 -0000	1.12
  @@ -179,28 +179,28 @@
   <p>Differences</p>
   <ul>
     <li>Jelly has full support for pluggable expression languages. The default expression
language is a superset of the one
  -  	used in JSP, JSTL and JSF which supports conditional expressions, navigating bean properties,

  -  	and working with Maps, Collections, Lists, arrays etc. 
  -  	Jexl is the current implementation which adds some Velocity-like enhancements like method
calls on beans etc.
  -  	Jelly supports other expression and scripting languages like Velocity, beanshell, JavaScript,
Jython, pnuts, BSF etc in separate tag libraries
  +      used in JSP, JSTL and JSF which supports conditional expressions, navigating bean
properties, 
  +      and working with Maps, Collections, Lists, arrays etc. 
  +      Jexl is the current implementation which adds some Velocity-like enhancements like
method calls on beans etc.
  +      Jelly supports other expression and scripting languages like Velocity, beanshell,
JavaScript, Jython, pnuts, BSF etc in separate tag libraries
     </li>
     <li>Jelly has native XML support. Jelly can parse XML and process it using XPath
expressions (via the JSTL tags). 
  -  	Also Jelly supports a declarative model of processing XML (via the JSL tags) which is
similar to XSLT 
  -  	but can use Jelly tags, beans and Ant tasks inside the XML template in a similar way
to DVSL.</li>
  +      Also Jelly supports a declarative model of processing XML (via the JSL tags) which
is similar to XSLT 
  +      but can use Jelly tags, beans and Ant tasks inside the XML template in a similar
way to DVSL.</li>
     <li>
  -  	Jelly has a much more powerful collaboration mechanism for passing information between
tags/tasks. 
  -  	In Jelly variables can be any object plus variable scopes can be nested to allow nested
scripts to work together neatly.
  -  	A tag/task can be customized with beans as well as being able to consume, emit, filter
and transform XML.
  -  	So Jelly tags can be configured from and can collaborate with beans and XML.
  +      Jelly has a much more powerful collaboration mechanism for passing information between
tags/tasks. 
  +      In Jelly variables can be any object plus variable scopes can be nested to allow
nested scripts to work together neatly.
  +      A tag/task can be customized with beans as well as being able to consume, emit, filter
and transform XML.
  +      So Jelly tags can be configured from and can collaborate with beans and XML.
     </li>
     <li>Jelly supports dynamic tags. Tags can be defined in Jelly script to avoid repetitive
typing 
  -	such as to wrap up most of the complexity of making a SOAP call. So Jelly has an integrated
tag based macro facility.
  +    such as to wrap up most of the complexity of making a SOAP call. So Jelly has an integrated
tag based macro facility.
     </li>
     <li>
  -  	Jelly uses XML namespaces to allow lots of different tag libraries to work together
seamlessly in the same 
  -  	XML document. This means you can mix and match Ant tasks with JSTL and Jelly tag libraries.

  -  	All can use their own expression languages, so one script could mix and match the expression
languages 
  -  	from Ant and JSTL as well as XPath and Jython.
  +      Jelly uses XML namespaces to allow lots of different tag libraries to work together
seamlessly in the same 
  +      XML document. This means you can mix and match Ant tasks with JSTL and Jelly tag
libraries. 
  +      All can use their own expression languages, so one script could mix and match the
expression languages 
  +      from Ant and JSTL as well as XPath and Jython.
     </li>
     <li>There is a clear difference of emphasis. Ant is a build system, Jelly is a
scripting engine.
     </li>
  @@ -214,14 +214,14 @@
   <p>Jelly has various possible uses. Here's a few to think about</p>
   <ul>
     <li>An additional tool for Ant users to provide more flexible Ant scripting. 
  -  	Indeed Jelly is already used in Maven to provide a more flexible build system 
  -  	while still preserving existing investment in Ant tasks.
  +      Indeed Jelly is already used in Maven to provide a more flexible build system 
  +      while still preserving existing investment in Ant tasks.
     </li>
     <li>HTTP, JMS, SOAP, XML and SQL based unit testing framework similar to Latka
and AntEater</li>
     <li>SOAP scripting or XML processing engine</li>
     <li>XML or page templating system, possibly a Generator for Cocoon</li>
     <li>Alternative (very lightweight) implementation of JSTL that can be run from

  -  	Ant to generate static content</li>
  +      Ant to generate static content</li>
     <li>A workflow, EAI or integration, maybe integrated into commons-workflow</li>
     <li>Code generation system, maybe an enhanced scripting engine for XDoclet</li>
   </ul>
  
  
  
  1.23      +59 -59    jakarta-commons/jelly/xdocs/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/todo.xml,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- todo.xml	25 Feb 2004 01:10:23 -0000	1.22
  +++ todo.xml	8 Sep 2004 05:40:45 -0000	1.23
  @@ -31,82 +31,82 @@
         
       <section name="Core tasks"> 
         <ul>
  -		<li>Implementa a META-INF/services mechanism for mapping Jelly libraries to namespace
URIs
  -			in a similar way to how the commons-discovery and JAXP libraries work.
  -			This would allow Jelly libraries to be distributed in a self contained JAR then just
put
  -			on the classpath and they'd be usable.				
  -		</li>
  -		<li>
  -			Implement a JJAR/Maven mechanism so that using a new Jelly library via a namespace URI
would
  -			automatically download the jar and its dependencies from some local/remote repository.
  -		</li>
  -		<li>Maybe add a Scope class to make it easier to plugin custom scopes such as 
  -			request, session, applicaiton, initParams, params, transation etc.
  -			In a workflow setting this could also include transient and persistent scopes
  -		</li>
  -		<li>Write a JellyServlet so that Jelly can be used as a page templating system.
  -		</li>
  -		<li>Implement a HTML parser for Jelly, probably using NeckoHTML so that non-XML
can be parsed
  -			and tags with prefixes can be bound to Jelly tags.
  -		</li>
  +        <li>Implementa a META-INF/services mechanism for mapping Jelly libraries
to namespace URIs
  +            in a similar way to how the commons-discovery and JAXP libraries work.
  +            This would allow Jelly libraries to be distributed in a self contained JAR
then just put
  +            on the classpath and they'd be usable.                
  +        </li>
  +        <li>
  +            Implement a JJAR/Maven mechanism so that using a new Jelly library via a namespace
URI would
  +            automatically download the jar and its dependencies from some local/remote
repository.
  +        </li>
  +        <li>Maybe add a Scope class to make it easier to plugin custom scopes such
as 
  +            request, session, applicaiton, initParams, params, transation etc.
  +            In a workflow setting this could also include transient and persistent scopes
  +        </li>
  +        <li>Write a JellyServlet so that Jelly can be used as a page templating system.
  +        </li>
  +        <li>Implement a HTML parser for Jelly, probably using NeckoHTML so that non-XML
can be parsed
  +            and tags with prefixes can be bound to Jelly tags.
  +        </li>
           <li>write a Cocoon JellyGenerator so that Jelly scripts can be used easily
inside Cocoon</li>
  -		<li>consider implementing a Jelly Doclet so that Jelly can be used to code generate
  -			stuff from javadoc tags in a similar way to XDoclet but making use of the JSTL tags
and
  -			the Velocity like expression language (Jexl) which will avoid the need to use huge numbers

  -			of tags.				
  -		</li>
  -		<li>Rename the DynaTag interface to be DynamicAttributes along with JSP1.3, 
  -			also add a namespace URI parameter
  -		</li>
  -		<li>Add support for namespace URI use inside XPath expressions.</li>
  -		<li>When defining new tags using &lt;define:tag&gt;, we should allow attributes
to be named,<br/>
  -			specified as required, specify the optional conditions and so forth for validating instances.<br/>

  -			I guess this could just be normal script though.
  -		</li>
  -		<li>The org.apache.commons.jelly.impl package doesn't have a great name - <br/>
  -			Can we think of a better one? <br/>
  -			Also some of the classes in this package could maybe do with a rename? <br/>
  -			ScriptBlock for example - should we just call it a Block or maybe a CompositeScript?
  -		</li>
  -		<li>Add an adapter to run JSP tag libraries inside Jelly when Jelly is used in
a 
  -			Servlet / JSP environment?
  -		</li>
  -		<li>Document much more!</li>
  -	  </ul>
  +        <li>consider implementing a Jelly Doclet so that Jelly can be used to code
generate
  +            stuff from javadoc tags in a similar way to XDoclet but making use of the JSTL
tags and
  +            the Velocity like expression language (Jexl) which will avoid the need to use
huge numbers 
  +            of tags.                
  +        </li>
  +        <li>Rename the DynaTag interface to be DynamicAttributes along with JSP1.3,

  +            also add a namespace URI parameter
  +        </li>
  +        <li>Add support for namespace URI use inside XPath expressions.</li>
  +        <li>When defining new tags using &lt;define:tag&gt;, we should allow
attributes to be named,<br/>
  +            specified as required, specify the optional conditions and so forth for validating
instances.<br/> 
  +            I guess this could just be normal script though.
  +        </li>
  +        <li>The org.apache.commons.jelly.impl package doesn't have a great name -
<br/>
  +            Can we think of a better one? <br/>
  +            Also some of the classes in this package could maybe do with a rename? <br/>
  +            ScriptBlock for example - should we just call it a Block or maybe a CompositeScript?
  +        </li>
  +        <li>Add an adapter to run JSP tag libraries inside Jelly when Jelly is used
in a 
  +            Servlet / JSP environment?
  +        </li>
  +        <li>Document much more!</li>
  +      </ul>
       </section>
         
       <section name="Ideas for new tag libraries"> 
         <ul>
           <li>
  -        	An XSD tag library that can be used to parse XSD documents and create DynaBeans
from the complex types.
  +            An XSD tag library that can be used to parse XSD documents and create DynaBeans
from the complex types.
   <pre>
   &lt;xsd:element name="MyDynamicClass"&gt;
     &lt;xsd:complexType&gt;
  -  	...
  +      ...
     &lt;/xsd:complexType&gt;
   &lt;/xsd:element&gt;</pre>
   
  -			Also we could consider using class names or XSD type names to do conversions of values,
maybe using
  -			the ConvertUtils class in beanutils.
  +            Also we could consider using class names or XSD type names to do conversions
of values, maybe using
  +            the ConvertUtils class in beanutils.
           </li>
           <li>conside a tag library which implements the <a href="http://stx.gingerall.cz/stx/index.html">STX</a>
  -        	specification for the SAX based transformation of XML. This is kinda like XPath
and XSLT but is based
  -        	purely on a SAX stream. Maybe we could wrap <a href="http://www.obqo.de/joost">Joost</a>
  -        	in a Jelly tag library
  -		</li>
  +            specification for the SAX based transformation of XML. This is kinda like XPath
and XSLT but is based
  +            purely on a SAX stream. Maybe we could wrap <a href="http://www.obqo.de/joost">Joost</a>
  +            in a Jelly tag library
  +        </li>
           <li>Implement a Schematron tag library for validing XML using a path based
approach, rather than schema based.</li>
           <li>
  -        	Provide support for running a piece of Jelly script remotely. This would be particularly
useful for distributed
  -        	testing. Maybe integrating or enhancing something like 
  -        	<a href="http://sourceforge.net/projects/remoteant">rant</a>
  +            Provide support for running a piece of Jelly script remotely. This would be
particularly useful for distributed
  +            testing. Maybe integrating or enhancing something like 
  +            <a href="http://sourceforge.net/projects/remoteant">rant</a>
           </li>
  -	  </ul>
  +      </ul>
       </section>
   
       <section name="Changes to existing tag libraries"> 
         <ul>
  -		<li>Add JSL test cases to test for ordering of patterns and that the correct output
comes out.</li>
  -	  </ul>
  +        <li>Add JSL test cases to test for ordering of patterns and that the correct
output comes out.</li>
  +      </ul>
       </section>
   
       <section name="Ponder about"> 
  @@ -115,12 +115,12 @@
         </p>
         <ul>
           <li>
  -			maybe consider a tag which will switch the default EL to XPath; then XPath and EL can
be peers. Then ${foo}
  -			can be used as an XPath expression anywhere
  -		</li>
  +            maybe consider a tag which will switch the default EL to XPath; then XPath
and EL can be peers. Then ${foo}
  +            can be used as an XPath expression anywhere
  +        </li>
           <li>We could autogenerate XML Schemas or RelaxNG docs for tag libraries to
help validate scripts</li>
           <li>Patch TagLibrary to alias all &lt;mixedCase&gt; tags to &lt;mixed-case&gt;
 tags</li>
  -	  </ul>
  +      </ul>
       </section>
       
       </section>
  
  
  
  1.12      +27 -27    jakarta-commons/jelly/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/faq.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- faq.xml	25 Feb 2004 01:10:23 -0000	1.11
  +++ faq.xml	8 Sep 2004 05:40:45 -0000	1.12
  @@ -131,12 +131,12 @@
       <section name="Using Jelly">
         <dl>
           <dt>
  -					<a name="calling-jelly">
  -						How do I call Jelly from Java code?
  -					</a>
  +                    <a name="calling-jelly">
  +                        How do I call Jelly from Java code?
  +                    </a>
           </dt>
           <dd>
  -        	Try the following code. Note that the runScript() method below is overloaded and
can take a File, URL etc.
  +            Try the following code. Note that the runScript() method below is overloaded
and can take a File, URL etc.
   <code>
   <source>
   // pass the output of the script somewhere
  @@ -152,46 +152,46 @@
   
         <dl>
           <dt>
  -					<a name="command-line">
  -						How do I invoke Jelly from the command line?
  -					</a>
  +                    <a name="command-line">
  +                        How do I invoke Jelly from the command line?
  +                    </a>
           </dt>
           <dd>
  -        	When you build a binary disitribution of Jelly, 
  -        	there is a jelly script which works on Windows and Unixes to run Jelly.
  -        	You can create a binary distribution of Jelly via
  -        	<code>
  -        		maven dist
  -        	</code>
  +            When you build a binary disitribution of Jelly, 
  +            there is a jelly script which works on Windows and Unixes to run Jelly.
  +            You can create a binary distribution of Jelly via
  +            <code>
  +                maven dist
  +            </code>
           </dd>
           <dd>
  -        	All you really need to do is to invoke the 
  -        	<i>org.apache.commons.jelly.Jelly</i> class from the command line
  -        	with a correct classpath.
  +            All you really need to do is to invoke the 
  +            <i>org.apache.commons.jelly.Jelly</i> class from the command line
  +            with a correct classpath.
           </dd>
         </dl>
         <dl>
           <dt>
  -					<a name="invoke-ant">
  -						How do I invoke Jelly from inside Ant?
  -					</a>
  +                    <a name="invoke-ant">
  +                        How do I invoke Jelly from inside Ant?
  +                    </a>
           </dt>
           <dd>
  -        	There is an Ant task that comes with the Ant library called
  -        	<i>org.apache.commons.task.JellyTask</i> which can be taskdef'd in
any Ant script.
  +            There is an Ant task that comes with the Ant library called
  +            <i>org.apache.commons.task.JellyTask</i> which can be taskdef'd
in any Ant script.
           </dd>
         </dl>
   
         <dl>
           <dt>
  -					<a name="invoke-maven">
  -						How do I invoke Jelly from inside Maven?
  -					</a>
  +                    <a name="invoke-maven">
  +                        How do I invoke Jelly from inside Maven?
  +                    </a>
           </dt>
           <dd>
  -        	Maven's maven.xml file is actually a Jelly script; so you can include any Jelly
script
  -        	inside any of the Maven goals. So if you want to execute a specific Jelly script
you can
  -        	just &lt;j:include uri="foo.jelly" &gt; it inside the maven.xml.
  +            Maven's maven.xml file is actually a Jelly script; so you can include any Jelly
script
  +            inside any of the Maven goals. So if you want to execute a specific Jelly script
you can
  +            just &lt;j:include uri="foo.jelly" &gt; it inside the maven.xml.
           </dd>
         </dl>
   
  
  
  
  1.9       +5 -5      jakarta-commons/jelly/xdocs/jellyunit.xml
  
  Index: jellyunit.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/jellyunit.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- jellyunit.xml	25 Feb 2004 01:10:23 -0000	1.8
  +++ jellyunit.xml	8 Sep 2004 05:40:45 -0000	1.9
  @@ -58,9 +58,9 @@
           <a href="http://cvs.apache.org/viewcvs.cgi/jakarta-commons/jelly/jelly-tags/betwixt/src/test/org/apache/commons/jelly/betwixt/common.jelly?rev=HEAD">here</a>
         </p>
         <p>
  -      	The <a href="libs/validate/tags.html">validate</a> library can be used
to perform XML validation inside JellyUnit.
  -      	For example there's an example JellyUnit script validating XML 
  -      	<a href="http://cvs.apache.org/viewcvs/jakarta-commons/jelly/jelly-tags/validate/src/test/org/apache/commons/jelly/tags/validate/suite.jelly?rev=HEAD">here</a>
  +          The <a href="libs/validate/tags.html">validate</a> library can be
used to perform XML validation inside JellyUnit.
  +          For example there's an example JellyUnit script validating XML 
  +          <a href="http://cvs.apache.org/viewcvs/jakarta-commons/jelly/jelly-tags/validate/src/test/org/apache/commons/jelly/tags/validate/suite.jelly?rev=HEAD">here</a>
         </p>
       </section>
   
  @@ -99,12 +99,12 @@
           which you can derive from
           to produce a single Java class which has a static <i>suite()</i> method
to create a TestSuite object 
           containing all the test cases created by the JellyUnit files.
  -		There is an 
  +        There is an 
           <a href="http://cvs.apache.org/viewcvs.cgi/jakarta-commons/jelly/jelly-tags/junit/src/test/org/apache/commons/jelly/junit/TestJUnit.java?rev=HEAD">example</a>
           of this in action.
         </p>
         <p>So if you had a test suite defined in a jelly script <a>suite.jelly</a>
in a package com.acme.foo
  -      	then you could create a class, capable of being ran inside any JUnit test runner
framework as follows
  +          then you could create a class, capable of being ran inside any JUnit test runner
framework as follows
         </p>
   <source>
   package com.acme.foo;
  
  
  
  1.5       +2 -2      jakarta-commons/jelly/xdocs/gettingstarted.xml
  
  Index: gettingstarted.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/gettingstarted.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- gettingstarted.xml	25 Feb 2004 01:10:23 -0000	1.4
  +++ gettingstarted.xml	8 Sep 2004 05:40:45 -0000	1.5
  @@ -28,7 +28,7 @@
   
   
   <p>
  -The easiest way to get started with Jelly is to try out the <a href="tutorial.html">tutorials</a>.

  +The easiest way to get started with Jelly is to try out the <a href="tutorial.html">tutorials</a>.
   
   Before you try out any of the tutorials, you'll need to install Maven first.
   For more details on how to install Maven please refer to the 
   <a href="http://maven.apache.org/">Maven documentation</a>
  @@ -93,7 +93,7 @@
       changing the environment variable MAVEN_OPTS (e.g. to -Xmx768m...) might help.
       </p>
   <p>
  -Once you've got this far, it might be time to try out one of the <a href="tutorial.html">tutorials</a>

  +Once you've got this far, it might be time to try out one of the <a href="tutorial.html">tutorials</a>
   
   </p>
   </section>
   
  
  
  
  1.5       +3 -3      jakarta-commons/jelly/xdocs/jellyswt.xml
  
  Index: jellyswt.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/jelly/xdocs/jellyswt.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- jellyswt.xml	25 Feb 2004 01:10:23 -0000	1.4
  +++ jellyswt.xml	8 Sep 2004 05:40:45 -0000	1.5
  @@ -57,7 +57,7 @@
       </section>
       
       <section name="Useful SWT Links"> 
  -    	<ul>
  +        <ul>
         <li>
           <a href="http://www.eclipse.org/documentation/html/plugins/org.eclipse.platform.doc.isv/doc/reference/api/index.html">SWT
Javadoc</a> 
           is very handy. Its mostly the widgets package thats of most interest.
  @@ -66,9 +66,9 @@
           This <a href="http://eclipsewiki.swiki.net/2">SWT Wiki</a> has lots
of good examples and documentation.
         </li>
         <li>
  -      	This <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-swt-home/dev.html">page</a>
also has a list of lots of little example SWT applications.
  +          This <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-swt-home/dev.html">page</a>
also has a list of lots of little example SWT applications.
         </li>
  -    	</ul>
  +        </ul>
       </section>
       
     </body>
  
  
  

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


Mime
View raw message