What's New in 1.4.0
There are a number of enhancements and fixes in this version.
- You can now apply a pattern to any Eclipse resource. If the resource is a file with a parsable
filetype (.appdef, .xml, .java) then the file is parsed and the pattern is applied to the resulting
DOM. This is what used to happen with .appdef files anyway. In all other cases, a simple appdef
containing a root <app> element and a single nested <project>, <folder> or <file>
element is merged with the pattern.
- You may define new parsable file types by extending the com.ibm.dptk.appdefType extension point in your
own plugin. The extension point lets you specify a file type and the fully qualified class name of a class
that can parse files of that type and return a DOM.
- The content assist for .pat files has been fixed for Eclipse 2.1. You can use CTRL-space to
request a list of template tags that match the previous few characters at the cursor.
- Pattern developers can now declare sample appdefs and deploy them with the pattern. A new resource
wizard in the "Design Pattern Toolkit" category lets the user pick from the set of declared samples
from all available patterns and will copy that appdef example into a specified file. This lets pattern
developers easily describe by example the appdefs necessary for their patterns.
- A prototype "Exemplar Analysis" tool is available to help pattern developers build pattern templates
and an initial appdef file. This prototype is still under development, but does provide tooling support
for the initial stages of pattern development.
- A new <stringTokens> tag lets you iterate over the tokens in a specified string.
- Attribute values containing double quotes are now written out enclosed in single quotes
- The <milliseconds> tag now works.
- The export pattern as patzip action now copies all project files to the patzip file.
© Copyright IBM Corporation 2000,
2005. All Rights Reserved.