LICENSE.html
|
DocFlex Software License |
README.html
|
this file |
doc/
|
DocFlex/XML & DocFlex Technology Documentation |
*.bat
|
Files prepared for Windows Installation: |
designer.bat
|
|
generator.bat
|
|
update_templates.bat
|
|
linux/
|
Files prepared for Linux Installation: |
linux/designer.sh
|
|
linux/generator.sh
|
|
linux/update_templates.sh
|
|
linux/docflex.config
|
|
ant/
|
Ant example files: |
ant/build.xml
|
|
ant/make.bat
|
|
ant/make.sh
|
|
lib/
|
Runtime Environment: |
lib/docflex-xml.jar
|
|
lib/docflex.config
|
|
lib/xml-apis.jar
|
|
config/
|
Configuration files (created and updated dynamically): |
config/designer.config
|
|
config/generator.config
|
|
templates/
|
template applications |
templates/XMLDoc/
|
The "XML File Documentor" (XMLDoc) template set: |
templates/XMLDoc/PlainDoc.tpl
|
|
templates/XMLDoc/FramedDoc.tpl
|
|
templates/XMLDoc/xmldoc.xmltype
|
|
templates/XSDDoc/
|
The "XML Schema Documentation Generator" (XSDDoc) template set.
For more details, see:
templates/XSDDoc/README.html
|
samples/
|
Demo samples: |
samples/sales/
|
|
samples/personal/
|
|
samples/HumanEvolution/
|
|
You can freely download Java from Sun Java Technology web-site: http://java.sun.com
DocFlex/XML is a pure Java application. The Template Designer GUI is implemented entirely using Swing. Therefore, everything is supposed to work on any operating system where Java2 Runtime Environment can be installed.
Specifically, the software includes both MS Windows BAT files and Linux shell script files to run DocFlex/XML immediately on those operating systems. See Windows Installation and Linux Installation respectively.
We were also reported that DocFlex/XML worked successfully under Mac OS X.
To parse XML files, DTDs and XML Schemas, DocFlex/XML uses Apache Xerces2 Java Parser version 2.9.0. In the case of any questions concerning this library, please refer to the Apache Xerces home page: http://xerces.apache.org.
To generate XML schema documentation (for big and middle sized XML schemas) using XSDDoc template set, you may need a powerful enough computer (e.g. with Intel Pentium 4 or AMD Athlon processor) and at least 512 MB RAM memory.
| Note: | If you have a license for "XSDDoc" template application, you will be able to run it also in full mode even without a special license for DocFlex/XML itself. |
| Note: | To use XSDDoc without limitations, a separate license for it is required. |
However, you may use or further modify your trial templates once you have installed a Commercial or Academic License for DocFlex/XML.
In addition, the Commercial License will allow you to clear your templates created/modified in trial mode from the limitation on execution by the reduced edition. To do this, you should resave the templates with the Template Designer after installing the new license.
You can use update_templates.bat to upgrade all your templates at once in a batch mode.
For more details, see the Template Designer command line options
(you can use also '-?' argument in designer.bat).
*.bat files in DocFlex/XML root directory
to specify the JAVA_HOME variable according to the location of
Java 6, Java 5 or Java 1.4.x installed on your system.
DFH variable to the absolute pathname
of the DocFlex/XML installation directory (e.g. set DFH=C:\docflex-xml-1.7.0).
'docflex-xml.license', which you must have
received by e-mail, to lib directory. This file should be always near
the docflex-xml.jar file!
designer.bat to launch Template Designer
or generator.bat to run the template applications or samples.
*.sh shell script files contained in linux
subdirectory to specify the JAVA_HOME variable according to the location of
Java 6, Java 5 or Java 1.4.x installed on your system.
For each shell script file, edit its "Permission" properties to allow it to be executed by Linux.
'docflex-xml.license', which you must have
received by e-mail, to lib directory. This file should be always near the
docflex-xml.jar file!
designer.sh or generator.sh !
generator.bat. You will see the generator dialog.
XMLDoc.tpl template.
Each XML file can be specified either by local path name or by URL. In the case of a URL, the generator will try to download such a file directly from the Internet. When multiple XML files are specified, make sure that each pathname or URL is enclosed in double quotes.
templates/XSDDoc/README.html | Running XSDDoc
designer.bat)
| Sample | XML File | Template |
|---|---|---|
| Sales Report |
samples/sales/sales.xml
|
samples/sales/sales.tpl
|
| Alternative to XSLT |
samples/personal/personal.xml
|
samples/personal/personal.tpl
|
| XML Schema of Human Evolution |
samples/HumanEvolution/HumanEvolution.xsd
|
Run with both templates/XSDDocFrames.tpl (HTML output)
and templates/XSDDoc.tpl (RTF output).
This will look fun!
|
Check the latest releases and documentation updates at: www.filigris.com.
See: templates/XSDDoc/README.html | Change Log | Version 2.0.0
A new licensing system has been implemented with the support of multiple licenses (that cover different features within the same software package) and a possibility to attach licenses to particular sets of templates (commercial template application).
The goal is both to allow our customers to pay exactly for what they are willing to use and to provide us with more resources for further development of this software.
Note: Any old commercial licenses for DocFlex/XML will work the same. If you have one, you may install and use it with this version as well.
As the number of template parameters (controlling what is generated) ever grows, the Template Parameter Inspector in its previous form became increasingly cumbersome and difficult to navigate.
This problem has been addressed by introducing a possibility to collapse/expand the parameter group nodes dynamically
(some of which can be preset in the templates to appear initially in the collapsed form;
further, the current collapse/expand state of particular group nodes is saved in the
generator.config and restored next time).
What is more, now some of the parameter group nodes may themselves serve as the template parameters.
These improvements allow introducing lots of parameters so as to control a particular big template application. Those parameters may be organized in the form of a hierarchical tree, which is both compact and easy to navigate.
This feature may not sound very great, but it was not that easy to implement. In fact, it substantially speeds up the process of designing of templates (which we particularly need ourselves as the primary users of our own tool).
See: templates/XSDDoc/README.html | Change Log | Version 1.6.8
config/xmltypes.config file)
to any number of XML Type Configuration Files.
Now, a complete XML Type definition (which includes the XML schemas describing the particular
XML data source) can be stored together with the template set based on it and loaded dynamically when needed.
This makes possible to represent a particular template application in the form of a single software unit
that can be easily distributed and deployed by its own.
See: templates/XSDDoc/README.html | Change Log | Version 1.6.7
java.lang.ClassCastException exception
happening when a schema with unspecified (i.e. global) target namespace imported another schema using
<xs:include> directive.
In templates, the new image size must be specified in device-independent units (like points). Before that, it was an HTML browser who converted points into pixels, which might be responsible for producing images with unpredictable sizes.
Now, when generating HTML, the DocFlex generator itself converts point size into pixel size according to the DPI value specified in the formatting properties of the given templates (see: Template Designer | File | Properties | Formatting | General | Resolution (DPI)). So, in HTML, the new image size will always be specified in pixels.
Now, all supported image formats include: GIF, PNG, JPG, WMF, BMP
This open source Java library is used by DocFlex/XML (all editions) and included in the package (see Package Contents). Support of the newest version of Apache Xerces will help to integrate DocFlex/XML seamlessly with the latest versions of other important tools (e.g. Apache Ant).
The bug happened when DocFlex/XML home directory was placed inside another directory
whose name contained a space (e.g. 'C:\Program Files\docflex-xml').
It caused java.io.FileNotFoundException during opening the configuration files.
Now, this is working.
See: templates/XSDDoc/README.html | Change Log | Version 1.6.3
align attribute of an <img> tag in
a description preformatted with HTML/XHTML markup.
(See Image Control Properties Dialog | Formatting | Image tab).
firstSentence() function, which extracts the first sentence
from a long description text to be placed in a summary table, has been totally redeveloped.
Now, it recognizes the HTML markup and finds the first sentence boundary according
to the pure text extracted from the original string (i.e. without HTML tags) as well as
stops on any HTML block tag (such as <p>). In the returned string, the original HTML
markup is preserved and unfinished HTML elements are correctly closed.
(See Template Designer | Help | Expression Assistant dialog for more info).
OutputFormat.renderEmbeddedHTML has been added
to indicate if "Render embedded HTML" format option has been specified for the generator.
Now, this property is used in XSDDoc templates
to better control processing of XHTML in XML schema annotations.
stderr (by default) or in a separate 'docflex_error.log' file
(when it is specified with the newly introduced -errlog option).
GOMIterator.prevItem and GOMIterator.nextItem
were introduced as well as a method accompanying them:
GOMIterator.itemAt().
DSMElement.rawValue and
DSMAttr.rawValue. These properties allow accessing the unprocessed
text values of XML elements/attributes directly obtained from the XML files.
You can use this, for instance, like the following:
contextElement.dsmElement.rawValue
(e.g. in the Formula Expression of a Data Control).
For details, see Template Designer | Help | Expression Assistant dialog.
See: templates/XSDDoc/README.html | Change Log | Version 1.6
All generator properties accessible within FlexQuery expressions (> 100) as well as all general (148) and XML-specific (18) FlexQuery functions are fully documented now. In total this took writing more than 330 KB of explanations in HTML!
You can find everything at the Template Designer | Help | Assistant dialog.
The first version DocFlex/XML has been released, which started the third and the most advanced product line based on DocFlex Technology. (The previous two, DocFlex/Javadoc and DocFlex/Together, had been already available for more than a year before that.)
Most of the document formatting capabilities was already in place. All processing of XML files was already based on the data type information obtained from DTD or XML Schemas. However, the actual data sources possible to process at once with a single template were limited to only one XML file.
The "Sales Report" and "Alternative to XSLT" samples are coming from those times.