[prev in list] [next in list] [prev in thread] [next in thread]
List: jakarta-oro-dev
Subject: cvs commit: jakarta-oro/xdocs/stylesheets project.xml
From: dfs () apache ! org
Date: 2001-05-18 8:30:47
[Download RAW message or body]
dfs 01/05/18 01:30:46
Modified: xdocs/stylesheets project.xml
Added: xdocs demo.xml devplan-2.0.xml status.xml
Log:
Added placeholders for status and development plan pages. Also added
a demo page for the Jakartaized version of the old OROMatcher demonstration
applet.
Revision Changes Path
1.1 jakarta-oro/xdocs/demo.xml
Index: demo.xml
===================================================================
<?xml version="1.0"?>
<!-- $Id: demo.xml,v 1.1 2001/05/18 08:30:37 dfs Exp $ -->
<document>
<properties>
<author>Daniel Savarese</author>
<title>Demonstration Applet</title>
</properties>
<body>
<section name="Demonstration Applet">
<center>
<applet codebase="classes" code="MatcherDemoApplet.class"
width="400" height="400">
<param name="fontSize" value="14"></param>
<param name="background" value="d2b48c"></param>
<hr></hr>
If you can't see the demo applet, please try enabling
Java in your browser.
<hr></hr>
</applet>
</center>
<p>
Jakarta ORO's text processing classes support a wide range
of features which are not demonstrated in this applet.
Here we allow you to test for yourself the Perl5, AWK, and glob
regular expression support from the org.apache.oro.text.regex,
org.apache.oro.text.awk, and org.apache.oro.text packages.
The Perl5 syntax demonstrated is Perl 5.003 compatible as of
version 2.0.2. Remember, Perl5 compatibility means that
zero-width lookahead assertions, greed control, backreferences,
and other features are supported. This applet only demonstrates
the basic functionality of the packages. The split and substitute
methods of the Util class and other features are not demonstrated
here. To get a better idea of what else you can do with Jakarta
ORO, you should look through the <a href="/api/index.html">API
documentation</a>.
</p>
</section>
<section name="Instructions">
<p>
Select a regular expression syntax in the topmost choice menu.
Type a regular expression in the first text field. Then in
the <b>Search Input</b> text area, enter text that you want to
search. Click the <b>Search</b> button to search the input text.
The results will appear in the <b>Search Results</b> text area.
The <b>Reset</b> button will clear the regular expression, input,
and result text.
</p>
<p>
There are two choice menus that affect the regular expression
search. The <b>contains()</b> item causes the
<code>contains()</code> method of the PatternMatcher interface to be
used to perform the search. This search is done in a while loop,
finding all pattern matches occuring within the input. The
<b>matches()</b> item causes the <code>matches()</code> method of
the PatternMatcher interface to be used to perform the search. The
<code>matches()</code> method only tests if all the input
<b>EXACTLY</b> matches the regular expression. It does not check
to see if there is a match somewhere inside the input. That is
what the <code>contains()</code> method is for. This is sometimes
a point of confusion for users who have tried other packages. In
Jakarta ORO, <code>matches()</code> is used to find exact matches,
and <code>contains</code> is used to find a match contained in the
input.
</p>
<p>
The <b>Case Sensitive</b> and <b>Case Insensitive</b> choice items
are self-explanatory. <b>Case Sensitive</b> causes the regular
expression to be compiled with case sensitivity enabled. <b>Case
Insensitive</b> causes the regular expression to treat upper and
lower case characters the same.
</p>
<p>
The <b>Search Results</b> text area will display all the matches
found in the input when the <b>contains()</b> choice item is
selected. It will also display what the parenthesized subgroups
of a regular expression matched. When the <b>matches()</b> choice
item is selected, only whether or not the input exactly matched
the pattern is indicated.
</p>
<p>
Please note that if you don't enter anything for a regular
expression, it will be compiled as an expression matching a
zero-length string (the null string), which will match before and
after every character in the input.
</p>
</section>
</body>
</document>
1.1 jakarta-oro/xdocs/devplan-2.0.xml
Index: devplan-2.0.xml
===================================================================
<?xml version="1.0"?>
<!-- $Id: devplan-2.0.xml,v 1.1 2001/05/18 08:30:39 dfs Exp $ -->
<document>
<properties>
<author>Daniel Savarese</author>
<title>Development Plan: 2.0 to 3.0</title>
</properties>
<body>
<section name="Development Plan: 2.0 to 3.0">
<p>
<em>The development plan is not ready yet, but the idea is that
we'll go through a series of iterative develop, test, bug
fix, test again, release, revisit objectives, cycles and
incrementally release stable versions of the software. The
primary objective of the work taking us from 2.0 through 2.1,
2.2, etc. up to 3.0 is to achive Perl 5.6 regular expression
compatibility in version 3.0 for the org.apache.oro.text.regex
and org.apache.oro.text.perl packages. This is the driving
force because the Perl expressions are the library's most
popular feature. Other development will transpire, but the
focus will be on the Perl regular expression support.</em>
</p>
<p>
<ol>
<li><a href="#Overview">Overview</a></li>
<ol>
<li><a href="#Purpose">Purpose</a></li>
<li><a href="#Deliverables">Deliverables</a></li>
</ol>
<li><a href="#Development Work">Development Work</a></li>
<ol>
<li><a href="#Regression and Unit Testing">
Regression and Unit Testing</a></li>
<li><a href="#Performance Testing and Optimization">
Performance Testing and Optimization</a></li>
<li><a href="#Defect Correction">Defect Correction</a></li>
<li><a href="#Functionality Enhancement">
Functionality Enhancement</a></li>
</ol>
<li><a href="#User Support">User Support</a></li>
<ol>
<li><a href="#Documentation">Documentation</a></li>
<li><a href="#Example Code">Example Code</a></li>
</ol>
<li><a href="#Code Development and Maintenance">
Code Development and Maintenance</a></li>
<ol>
<li><a href="#Code Cleanup">Code Cleanup</a></li>
<li><a href="#Committers">Committers</a></li>
</ol>
<li><a href="#Release Schedule">
Release Schedule</a></li>
<li><a href="#Beyond 3.0">Beyond 3.0</a></li>
</ol>
</p>
</section>
<section name="Overview">
<!--
<p>
The Jakarta ORO project has the goal of
</p>
-->
<subsection name="Purpose">
<!--
<ol>
<li>Achieve compatibily with Perl 5.6 regular expressions in
the org.apache.oro.text.regex and org.apache.oro.text.perl
packages.</li>
<li>Improve the performance of the org.apache.oro.text.regex
and org.apache.oro.text.perl packages.</li>
<li>Prevent the number of defects from increasing.</li>
<li>Make the package as easy to use as possible.</li>
</ol>
-->
</subsection>
<subsection name="Deliverables">
</subsection>
</section>
<section name="Development Work">
<subsection name="Regression and Unit Testing">
</subsection>
<subsection name="Performance Testing and Optimization">
</subsection>
<subsection name="Defect Correction">
</subsection>
<subsection name="Functionality Enhancement">
</subsection>
</section>
<section name="User Support">
<subsection name="Documentation">
</subsection>
<subsection name="Example Code">
</subsection>
</section>
<section name="Code Development and Maintenance">
<subsection name="Code Cleanup">
</subsection>
<subsection name="Committers">
</subsection>
</section>
<section name="Release Schedule">
</section>
<section name="Beyond 3.0">
</section>
</body>
</document>
1.1 jakarta-oro/xdocs/status.xml
Index: status.xml
===================================================================
<?xml version="1.0"?>
<!-- $Id: status.xml,v 1.1 2001/05/18 08:30:40 dfs Exp $ -->
<document>
<properties>
<author>Daniel Savarese</author>
<title>Project Status</title>
</properties>
<body>
<section name="Project Status">
<p>
Version 2.0.2 currently supports Perl 5.003 regular expressions
in the org.apache.oro.text.regex and org.apache.oro.text.perl
packages. The main development goal is to upgrade these
packages to support Perl 5.6 regular expressions. The
development plan will lay out the path to achieving this
objective and this status page will report the state of our
progress. Our current objective is to settle on a development
plan by June 11, 2001.
</p>
</section>
</body>
</document>
1.3 +10 -7 jakarta-oro/xdocs/stylesheets/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-oro/xdocs/stylesheets/project.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- project.xml 2001/05/17 00:44:44 1.2
+++ project.xml 2001/05/18 08:30:43 1.3
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<!-- $Id: project.xml,v 1.2 2001/05/17 00:44:44 dfs Exp $ -->
+<!-- $Id: project.xml,v 1.3 2001/05/18 08:30:43 dfs Exp $ -->
<project name="Jakarta ORO"
href="http://jakarta.apache.org/oro">
@@ -10,12 +10,9 @@
<body>
<menu name="About">
<item name="Overview" href="/index.html"/>
- <item name="Download"
- href="http://jakarta.apache.org/builds/jakarta-oro/release/"/>
- <!-- To be added
- <item name="Status"/>
- <item name="Development plan"/>
- -->
+ <item name="Development plan"
+ href="/devplan-2.0.html"/>
+ <item name="Status" href="/status.html"/>
<item name="Bug tracking" href="http://nagoya.apache.org/bugzilla/"/>
<item name="CVS"
href="http://jakarta.apache.org/cvsweb/index.cgi/jakarta-oro/"/>
@@ -23,6 +20,12 @@
href="http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-oro/CHANGES?content-type=text/plain"/>
<item name="License"
href="http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-oro/LICENSE?content-type=text/plain"/>
+ </menu>
+
+ <menu name="Software">
+ <item name="Download"
+ href="http://jakarta.apache.org/builds/jakarta-oro/release/"/>
+ <item name="Demonstration" href="/demo.html"/>
</menu>
<menu name="Community">
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic