commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons-sandbox/jelly/xdocs jellyswing.xml jellyunit.xml navigation.xml
Date Wed, 31 Jul 2002 11:42:47 GMT
jstrachan    2002/07/31 04:42:47

  Modified:    jelly/xdocs jellyunit.xml navigation.xml
  Added:       jelly/xdocs jellyswing.xml
  improved the navigation somewhat to make it easier to find things. Also added links to some
more examples as well as a little documentation on JellySwing
  Revision  Changes    Path
  1.4       +9 -1      jakarta-commons-sandbox/jelly/xdocs/jellyunit.xml
  Index: jellyunit.xml
  RCS file: /home/cvs/jakarta-commons-sandbox/jelly/xdocs/jellyunit.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- jellyunit.xml	22 Jul 2002 10:49:37 -0000	1.3
  +++ jellyunit.xml	31 Jul 2002 11:42:47 -0000	1.4
  @@ -29,9 +29,17 @@
           You can also use Ant FileSets and the <fileScanner> tag to iterate
over collections of 
           Jelly scripts or XML data files and use this data to define new test cases.
  +    </section>
  +    <section name="Examples"> 
  -        There is an example JellyUnit script
  +        There is a simple example JellyUnit script
           <a href="">here</a>
  +      </p>
  +      <p>
  +        An example demonstrating the use of the <a href="tags.html#jelly:betwixt">Betwixt</a>
library is 
  +        <a href="">here</a>
  +        along with a common shared test script
  +        <a href="">here</a>
       <section name="Integration with TestRunners"> 
  1.11      +4 -1      jakarta-commons-sandbox/jelly/xdocs/navigation.xml
  Index: navigation.xml
  RCS file: /home/cvs/jakarta-commons-sandbox/jelly/xdocs/navigation.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- navigation.xml	30 Jul 2002 14:46:29 -0000	1.10
  +++ navigation.xml	31 Jul 2002 11:42:47 -0000	1.11
  @@ -9,7 +9,6 @@
         <item name="Overview"                href="/index.html"/>
         <item name="FAQ"                     href="/faq.html"/>
         <item name="Detail"                  href="/overview.html"/>
  -      <item name="JellyUnit"               href="/jellyunit.html"/>
         <item name="Tag Reference"           href="/tags.html"/>
         <item name="Download"                href=""/>
         <item name="To Do List"              href="/todo.html"/>
  @@ -17,6 +16,10 @@
       <menu name="Community">
         <item name="News Blog"			   href=""/>
         <item name="IRC"					   href="/irc.html"/>
  +    </menu>
  +    <menu name="Libraries">
  +      <item name="JellyUnit"               href="/jellyunit.html"/>
  +      <item name="JellySwing"              href="/jellyswing.html"/>
  1.1                  jakarta-commons-sandbox/jelly/xdocs/jellyswing.xml
  Index: jellyswing.xml
  <?xml version="1.0"?>
      <author email="">James Strachan</author>
      <section name="JellySwing"> 
          JellySwing is a simple Jelly library which can be used to create Swing user interfaces.
          It allows XML documents (Jelly scripts) to be used to define the layout and rendering
of Swing 
          front ends which avoids lots of mundane Java coding, using markup to define the
          of your front end and allowing you to bind to Java code for the business objects
and models. 
          This mechanism uses seperation of concerns and MVC ideas from web applications,
allowing the rendering
          of your Swing front end to be easily transformed (since its XML) into different
styles while leaving your
          model and business objects untouched. It also allows different views to be constructed
independently of your models.
          There is an example JellySwing script
          <a href="">here</a>
          To try running the example type the following command then you should see a full
Swing user interface 
          appear with pull down menus, a splitter pane, a form, entry fields, buttons and
a table.
  	maven demo:swing
          This example even shows that simple actions can be coded in Jelly script too! Though
typically most
          complex logic and models (such as TableModel, TreeModel) should be written in Java
          Then Jelly script can be used to create the view and bind in the models.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message