summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpelder2006-03-22 12:43:49 (EST)
committer pelder2006-03-22 12:43:49 (EST)
commit711b4490e6f4fb11d737e948803ce75057eb4d7e (patch)
tree7b9e4b75f80abcb5118dfef33bd08671eb9c3b94
parenta1515a6b8d1c89796de75817f3f5b0555f521023 (diff)
downloadorg.eclipse.jet-711b4490e6f4fb11d737e948803ce75057eb4d7e.zip
org.eclipse.jet-711b4490e6f4fb11d737e948803ce75057eb4d7e.tar.gz
org.eclipse.jet-711b4490e6f4fb11d737e948803ce75057eb4d7e.tar.bz2
[132859] Cleaned up HTML to be HTML 4.0 strict compliant
-rw-r--r--plugins/org.eclipse.jet/html/whatsnew/changelog.html356
1 files changed, 215 insertions, 141 deletions
diff --git a/plugins/org.eclipse.jet/html/whatsnew/changelog.html b/plugins/org.eclipse.jet/html/whatsnew/changelog.html
index db3e210..f675ad7 100644
--- a/plugins/org.eclipse.jet/html/whatsnew/changelog.html
+++ b/plugins/org.eclipse.jet/html/whatsnew/changelog.html
@@ -1,111 +1,146 @@
-<html
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
+"http://www.w3.org/TR/html4/strict.dtd">
+<html>
<head>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
+<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
+type="text/css">
<title>What's New</title>
</head>
<body>
<h2>Build 20060216</h2>
<h3>**** WARNING *** PENDING PLUG-IN and PACKAGE CHANGES ****</h3>
-<p>
-The go ahead has been given to create a new Eclipse EMFT project, <code>org.eclipse.jet</code>, which will include the JET2 plugins.
-In the coming weeks, the following names will be changing as this project comes into being:
-<p>
+<p>The go ahead has been given to create a new Eclipse EMFT
+project, <code>org.eclipse.jet</code>, which will include the JET2
+plugins. In the coming weeks, the following names will be changing
+as this project comes into being:</p>
<table>
-<tr><td><b>Item</b></td><td><b>Old Name</b></td><td><b>New Name</b></td></tr>
-<tr><td>JET2 Core plug-in</td><td><code>org.eclipse.emf.jet2</code></td><td><code>org.eclipse.jet</code></td></tr>
-<tr><td>JET2 UI plug-in</td><td><code>org.eclipse.emf.jet2.ui</code></td><td><code>org.eclipse.jet.ui</code></td></tr>
-<tr><td>JET2 public APIs package names</td><td><code>org.eclipse.emf.jet2....</code></td><td><code>org.eclipse.jet...</code></td></tr>
+
+<tr>
+<td><b>Item</b></td>
+<td><b>Old Name</b></td>
+<td><b>New Name</b></td>
+</tr>
+<tr>
+<td>JET2 Core plug-in</td>
+<td><code>org.eclipse.emf.jet2</code></td>
+<td><code>org.eclipse.jet</code></td>
+</tr>
+<tr>
+
+<td>JET2 UI plug-in</td>
+<td><code>org.eclipse.emf.jet2.ui</code></td>
+<td><code>org.eclipse.jet.ui</code></td>
+</tr>
+<tr>
+<td>JET2 public APIs package names</td>
+<td><code>org.eclipse.emf.jet2....</code></td>
+<td><code>org.eclipse.jet...</code></td>
+</tr>
</table>
-<p>
-These changes will break a number of things:
-<bl>
-<li>JET2 Project natures and builder names change ids, making the JET2 compiler inoperative on existing JET2 projects.</li>
-<li>JET2 Projects will refer to the old JET2 plug-in, causing PDE compile errors.</li>
-<li>JET2 generated Java classes will refer to the old package names, and will need to be re-built.</li>
-<li>Plug-ins using the JET2 extension points will have to be updated to use the new plugins.</li>
-</bl>
-<p>
-<br>
-When the change happens, additional information (and hopefully tools) will be distributed on how to fix these problems.
-</p>
+<p>These changes will break a number of things:</p>
+<ul>
+<li>JET2 Project natures and builder names change ids, making the
+JET2 compiler inoperative on existing JET2 projects.</li>
+<li>JET2 Projects will refer to the old JET2 plug-in, causing PDE
+compile errors.</li>
+<li>JET2 generated Java classes will refer to the old package
+names, and will need to be re-built.</li>
+<li>Plug-ins using the JET2 extension points will have to be
+updated to use the new plugins.</li>
+</ul>
+<p>When the change happens, additional information (and hopefully
+tools) will be distributed on how to fix these problems.</p>
<h3>Functional changes</h3>
-<p>The JET2 editor has been removed. This is in prep for the move to Open Source - the editor is just
-not ready for prime time. If you have become attached to it's ideosyncratic behavior, let me know, I
-still have the code in a separate plug-in.
-</p>
+<p>The JET2 editor has been removed. This is in prep for the move
+to Open Source - the editor is just not ready for prime time. If
+you have become attached to it's ideosyncratic behavior, let me
+know, I still have the code in a separate plug-in.</p>
<h3>API Changes</h3>
-<bl>
-<li>An extension point <code>xpathFunctions</code> has been added to create additional XPath fuctions. Implmentations must implement
+<ul>
+<li>An extension point <code>xpathFunctions</code> has been added
+to create additional XPath fuctions. Implmentations must implement
<code>org.eclipse.emf.jet2.XPathFunction</code></li>
-</bl>
-
+</ul>
<h2>Build 20060208b</h2>
<h3>API Changes</h3>
-<bl>
-<li><code>TagInfo</code> has added an extra argument to its constructor to facilitate runtime tag execution tracing. The
-old constructor has been deprecated. <b>As this constructor is called by generated code, all JET2 projects should be re-built.</b>
-</li>
-<li><code>XPathContextExtender</code> now has extra methods <code>getAttributeValue</code>, <code>removeAttribute</code>,
-<code>getContents</code> and a new variant of <code>addTextElement</code>. See the java doc for details. This change
-will only be of interest to tag implementers.</li>
-</bl>
+<ul>
+<li><code>TagInfo</code> has added an extra argument to its
+constructor to facilitate runtime tag execution tracing. The old
+constructor has been deprecated. <b>As this constructor is called
+by generated code, all JET2 projects should be re-built.</b></li>
+<li><code>XPathContextExtender</code> now has extra methods
+<code>getAttributeValue</code>, <code>removeAttribute</code>,
+<code>getContents</code> and a new variant of
+<code>addTextElement</code>. See the java doc for details. This
+change will only be of interest to tag implementers.</li>
+
+</ul>
<h2>Build 20060208</h2>
<h3>API Changes</h3>
-<bl>
-<li>Internal package name changes. Most users should be unaffected.</li>
-<li>The code generator was creating a class _jet_transformation.java which used an
-internal interface <code>IJET2Transformation</code>. A new public interface has been
-introduced <code>JET2TemplateLoader</code>, and code generation has been changed.
-<b>Clean and rebuild you JET2 projects.</b></li>
-<li>The package <code>org.eclipse.emf.jet2.compile</code> has been renamed to
-<code>org.eclipse.emf.jet2.compiler</code>.
-</bl>
+<ul>
+<li>Internal package name changes. Most users should be
+unaffected.</li>
+<li>The code generator was creating a class
+_jet_transformation.java which used an internal interface
+<code>IJET2Transformation</code>. A new public interface has been
+introduced <code>JET2TemplateLoader</code>, and code generation has
+been changed. <b>Clean and rebuild you JET2 projects.</b></li>
+<li>The package <code>org.eclipse.emf.jet2.compile</code> has been
+renamed to <code>org.eclipse.emf.jet2.compiler</code>.</li>
+</ul>
<h3>New Features</h3>
-<bl>
-<li>The 'c:set' tag was not creating attributes on EMF-based models if the attribute name was not
-one defined in the model. This has been fixed.</li>
-<li>Primitive tag execution tracing is now available, but only by turning on plug-in tracing
-for <code>org.eclipse.emf.jet2</code>. This tracing should be expanded and enhanced in future builds.</li>
-</bl>
-
+<ul>
+<li>The 'c:set' tag was not creating attributes on EMF-based models
+if the attribute name was not one defined in the model. This has
+been fixed.</li>
+<li>Primitive tag execution tracing is now available, but only by
+turning on plug-in tracing for <code>org.eclipse.emf.jet2</code>.
+This tracing should be expanded and enhanced in future builds.</li>
+</ul>
<h2>Build 20060207</h2>
<h3>Bug Fixes</h3>
-<bl>
+<ul>
<li>Fixed loading of EMF-based input models.</li>
-</bl>
+</ul>
<h2>Build 20060203</h2>
<h3>API Changes</h3>
<h4>Tag Library Meta-data access</h4>
-The package <code>org.eclipse.emf.jet2.taglib</code> now contains a <code>TagLibraryManager</code>
-class that provides access to tag libraries declared in the platform. <b>This is valuable for editors
+The package <code>org.eclipse.emf.jet2.taglib</code> now contains a
+<code>TagLibraryManager</code> class that provides access to tag
+libraries declared in the platform. <b>This is valuable for editors
working on top of JET2.</b>
<h4>JET2Context refactoring</h4>
-The class <code>JET2Context</code> has been put on a diet. Many of the methods in it have been moved
-to <code>TransformContextExtender</code>. The goal (not there yet) is to have JET2Context light weight
-enough that a JET2 template can be evaluated in a Java program outside of Eclipse. <b>This change shouldn't
-affect anyone, except perhaps tag library authors</b>.
-<h4>Code generator refactoring</h4>
-The classes used by the code generator have been moved to public classes. Any 'internal' classes used
-by the code generator have been deprecated. <b>This should not affect anyone, although transforms that
-have not been 'cleaned' lately may have warnings about using deprecated methods.</b>
+The class <code>JET2Context</code> has been put on a diet. Many of
+the methods in it have been moved to
+<code>TransformContextExtender</code>. The goal (not there yet) is
+to have JET2Context light weight enough that a JET2 template can be
+evaluated in a Java program outside of Eclipse. <b>This change
+shouldn't affect anyone, except perhaps tag library authors</b>.
+<h4>Code generator refactoring</h4>
+The classes used by the code generator have been moved to public
+classes. Any 'internal' classes used by the code generator have
+been deprecated. <b>This should not affect anyone, although
+transforms that have not been 'cleaned' lately may have warnings
+about using deprecated methods.</b>
<h3>Code Generation Changes</h3>
-The code generator has changed. You should 'clean' your JET2 projects to get the latest code. <b>JET2
-is still compatible with the 'old' code, although there may be some warnings.</b>
+The code generator has changed. You should 'clean' your JET2
+projects to get the latest code. <b>JET2 is still compatible with
+the 'old' code, although there may be some warnings.</b>
<h2>Build 20060202</h2>
<h3>Deploying Transforms</h3>
<h4>New files</h4>
-<p>The New JET2 Project wizard has been enhanced to make JET2 transforms more easy to build.
-A new file <b>build.properties</b> is now created. Most users should not need to modify it.
-</p>
-<p>
-For existing projects, you should create a build.properties file with the following contents:
+<p>The New JET2 Project wizard has been enhanced to make JET2
+transforms more easy to build. A new file <b>build.properties</b>
+is now created. Most users should not need to modify it.</p>
+<p>For existing projects, you should create a build.properties file
+with the following contents:</p>
<pre>
source.. = jet2java/
output.. = bin/
@@ -117,93 +152,132 @@ src.includes = .project,\
build.properties,\
.classpath
</pre>
-</p>
+<br>
+
+<br>
<h4>Creating a deployable Transform</h4>
-<p>
-JET2 Transform projects can now be exported using the standard Eclipse plugin export tools. Steps to follow:
-<bl>
-<li>Right click over the project, and choose <b>Export...</b> from the context menu.</li>
-<li>In the export dialog, select <b>Plug-in Development -> Deployable Plug-ins and Fragments</b>, and click <b>Next</b></li>
-<li>Ensure your JET2 transform project is selected in the <b>Available Plug-ins and Fragments</b> list.</li>
-<li>Select the <b>Directory</b> button in the <b>Export Destination</b> group, and then select a directory to contain the exported
-transform (which will be a JAR file).</li>
-<li>In the <b>Export Options</b> group, ensure that <b>Package plug-ins as individual JAR archives</b> is selected.</li>
+<p>JET2 Transform projects can now be exported using the standard
+Eclipse plugin export tools. Steps to follow:</p>
+<ul>
+<li>Right click over the project, and choose <b>Export...</b> from
+the context menu.</li>
+<li>In the export dialog, select <b>Plug-in Development -&gt;
+Deployable Plug-ins and Fragments</b>, and click <b>Next</b></li>
+
+<li>Ensure your JET2 transform project is selected in the
+<b>Available Plug-ins and Fragments</b> list.</li>
+<li>Select the <b>Directory</b> button in the <b>Export
+Destination</b> group, and then select a directory to contain the
+exported transform (which will be a JAR file).</li>
+<li>In the <b>Export Options</b> group, ensure that <b>Package
+plug-ins as individual JAR archives</b> is selected.</li>
+
<li>Click <b>Finish</b></li>
-<li>If you have exported to a directory in your workspace, refresh the directory (select, and press F5).
-The exported JAR file will be in the <b>plugins</b> directory under the target directory.</li>
-</bl>
-</p>
+<li>If you have exported to a directory in your workspace, refresh
+the directory (select, and press F5). The exported JAR file will be
+in the <b>plugins</b> directory under the target directory.</li>
+</ul>
+<br>
+<br>
<h4>Deploying a transform in plug-in</h4>
-<p>
-Some transforms designed to be invoked from other Java code. (This is the case for the transform called by the New JET2 Project wizard.)
-In order to package such a transform with the Java code (which is assumed to be in a plug-in), the <b>org.eclipse.emf.jet2.deployedTransforms</b>
-extension point must be used. The following rules must be observed:
-<bl>
-<li>The exported transform JAR must be in a directory within the deploying plug-in project.</li>
-<li>The build.properties file for the deploying plug-in project must include the JAR file, or one of its
-containing directories in its binary build specification.</li>
-<li>The deploying plug-in project must include an extension to <b>org.eclipse.emf.jet2.deployedTransforms</b>.<li>
-</bl>
-</p>
-<p>
-As an example, the plugin org.eclipse.emf.jet2 deploys the transform org.eclipse.emf.jet2.newProject. The transform is exported
-to a JAR in the directory 'transforms/plugins/org.eclipse.emf.jet2.newProject_1.0.0.jar'. The build.properties file for org.eclipse.emf.jet2
-includes a reference to 'transforms' in its binary build. Finally, the plugin.xml contains:
+<p>Some transforms designed to be invoked from other Java code.
+(This is the case for the transform called by the New JET2 Project
+wizard.) In order to package such a transform with the Java code
+(which is assumed to be in a plug-in), the
+<b>org.eclipse.emf.jet2.deployedTransforms</b> extension point must
+be used. The following rules must be observed:</p>
+
+<ul>
+<li>The exported transform JAR must be in a directory within the
+deploying plug-in project.</li>
+<li>The build.properties file for the deploying plug-in project
+must include the JAR file, or one of its containing directories in
+its binary build specification.</li>
+<li>The deploying plug-in project must include an extension to
+<b>org.eclipse.emf.jet2.deployedTransforms</b>.</li>
+</ul>
+<br>
+<br>
+<p>As an example, the plugin org.eclipse.emf.jet2 deploys the
+transform org.eclipse.emf.jet2.newProject. The transform is
+exported to a JAR in the directory
+'transforms/plugins/org.eclipse.emf.jet2.newProject_1.0.0.jar'. The
+build.properties file for org.eclipse.emf.jet2 includes a reference
+to 'transforms' in its binary build. Finally, the plugin.xml
+contains:</p>
<pre>
&lt;extension
point="org.eclipse.emf.jet2.deployedTransforms"&gt;
+
&lt;deployedTransform
bundle="transforms/plugins/org.eclipse.emf.jet2.newproject_1.0.0.jar"
id="org.eclipse.emf.jet2.newproject"
private="true"/&gt;
&lt;/extension&gt;
</pre>
-</p>
-
+<br>
+<br>
<h3>Other Changes</h3>
-<bl>
-<li>The New Project Wizard new generates a file <b>plugin.xml</b>. At this point, no use is made of
-this file. However, this will eventually contain additional transform information such as:
-the initial template to run, a general transform description, which tag libraries are required and
-which tag libraries should be automatically imported into each template. Expect additional
+<ul>
+<li>The New Project Wizard new generates a file <b>plugin.xml</b>.
+At this point, no use is made of this file. However, this will
+eventually contain additional transform information such as: the
+initial template to run, a general transform description, which tag
+libraries are required and which tag libraries should be
+automatically imported into each template. Expect additional
capabilities in the next week or two.</li>
-</bl>
+</ul>
<h2>Build 20060127</h2>
<h3>Compiler</h3>
-<bl>
-<li>In build 20060126, the compiler was not writing new .java files (although it was successfully overwriting existing files).
-This has been fixed.</li>
-<li>Build 20060126 was missing an file essential for this change log to appear.</li>
-</bl>
-
+<ul>
+<li>In build 20060126, the compiler was not writing new .java files
+(although it was successfully overwriting existing files). This has
+been fixed.</li>
+<li>Build 20060126 was missing an file essential for this change
+log to appear.</li>
+</ul>
<h2>Build 20060126</h2>
<h3>Tag libraries</h3>
-<bl>
-<li>Bug in &lt;c:iterate&gt; causing cryptic error message about a variable not being set has been fixed.</li>
-<li>&lt;c:iterate&gt; now can accept a number or numeric expression in the 'select' field, and will iterate
-that number of times. The iteration variable will be a number, starting at 1, and incremented through
-each iteration.</li>
-<li>&lt;ws:copyFile&gt; has had some attributes renamed. You will get compiler errors & warnings until you
-fix things. Attribute 'url' becomes 'src'. Attribute 'urlContext' becomes 'srcContext'. Attribute 'path' becomes
-'target'.</li>
-<li>A bug in &lt;ws:copyFile&gt; when 'srcContext' is 'workspace' and 'target' is an absolute path (starts with
-'/') has been fixed.</li>
-<li>A bug in &lt;c:userRegion&gt; has been fixed. This now works as intended.</li>
-</bl>
+<ul>
+<li>Bug in &lt;c:iterate&gt; causing cryptic error message about a
+variable not being set has been fixed.</li>
+
+<li>&lt;c:iterate&gt; now can accept a number or numeric expression
+in the 'select' field, and will iterate that number of times. The
+iteration variable will be a number, starting at 1, and incremented
+through each iteration.</li>
+<li>&lt;ws:copyFile&gt; has had some attributes renamed. You will
+get compiler errors &amp; warnings until you fix things. Attribute
+'url' becomes 'src'. Attribute 'urlContext' becomes 'srcContext'.
+Attribute 'path' becomes 'target'.</li>
+<li>A bug in &lt;ws:copyFile&gt; when 'srcContext' is 'workspace'
+and 'target' is an absolute path (starts with '/') has been
+fixed.</li>
+<li>A bug in &lt;c:userRegion&gt; has been fixed. This now works as
+intended.</li>
+
+</ul>
<h3>Compiler</h3>
-<bl>
-<li>Compiler now warns about deprecated tag libraries, tags and attributes.</li>
-<li>Compiler now issues errors if tags that are empty should not be and vice versa.</li>
-<li>Bug in compiler was setting .jet files to 'derived'. This prevented CVS from checking these files
-by default. <b>For a few weeks, the compiler will automatically restore .jet files to be not derived.</b>
-</bl>
+<ul>
+<li>Compiler now warns about deprecated tag libraries, tags and
+attributes.</li>
+<li>Compiler now issues errors if tags that are empty should not be
+and vice versa.</li>
+<li>Bug in compiler was setting .jet files to 'derived'. This
+prevented CVS from checking these files by default. <b>For a few
+weeks, the compiler will automatically restore .jet files to be not
+derived.</b></li>
+</ul>
<h3>APIs</h3>
-<bl>
-<li>Tag library APIs have been refactored. I will add documentation next week. In the meantime, check out
-the Javadoc for ContainerTag, ConditionalTag and IteratingTag.</li>
-<li>The abstract implementation of IteratingTag, AbstractIteratingTag has had methods added to support
-easy creation of 'delimiter' attributes'.</li>
-</bl>
+<ul>
+<li>Tag library APIs have been refactored. I will add documentation
+next week. In the meantime, check out the Javadoc for ContainerTag,
+ConditionalTag and IteratingTag.</li>
+
+<li>The abstract implementation of IteratingTag,
+AbstractIteratingTag has had methods added to support easy creation
+of 'delimiter' attributes'.</li>
+</ul>
</body>
-</html> \ No newline at end of file
+</html>