FMPP 0.9.4 is out

Daniel Dekany <[email protected]> Fri, 2 Jan 2004 23:43:52 +0100
Newsgroups gmane.comp.text.fmpp
Message-ID <[email protected]>
FMPP 0.9.4 is released.

Download: http://prdownloads.sourceforge.net/fmpp/fmpp_0.9.4.tar.gz

New features, improvements:

* New setting: "localData"

  . Till now, all source files (all templates) have started with the
    same data model, the one you have specified with setting "data". With
    the new "localData" setting you can add variables to, and override the
    variables of the common data model, for groups of source files
    selected by path patterns.

  . This feature also let you attach a BeanShell script to a template,
    that can done some complex calculations before template execution,
    and put the results into the data model for the individual template.

  . Setting "templateData" is now deprecated.

  . Java API changes: New interface fmpp.LocalDataBuilder, deprecates
    fmpp.TemplateDataModelBuilder.

* Setting "borders" supports multiple layers. That is, multiple borders
  can be used at once for the same file.

* In <@pp.renameOutputFile ... /> you can use parameter extension
  instead of name, to change only the extension of the output file.

* Java API: TemplateEnvironment has new methods, most importantly
  static TemplateEnvironment getCurrentInstance() for accessing the
  current template environment in FreeMarker transforms/methods.

* Java API: New methods to Engine: Object getData(name) (returns
  unwrapped original values), Object removeData(name), cleatData()
  (deprecates misnamed clearSharedVariables()).

* Java API: Engine attribute that implements ProgressListener get
  notifications about engine events.

* Java API: fmpp.tdd.FunctionCall has public constructor now.

* Warning! Incompatible Java API change! Engine.getData(...) doesn't
  throw TemplateModelException anymore, because data wrapping is now
  deferred until the session execution.

* Warning! Incompatible Java API change! Synchronization was removed
  from Engine. It did the same as if you synchronize on the Engine
  instance and call the methods anyway...

* Warning! Incompatible Java API change!
  ProgressListener.notifyProgressEvent(...) is now allowed to throw
  Exception.

* More API documentation.

Bugfixes:

* <@pp.renameOutputFile ... /> has malfunctioned when the buffer was
  already flushed.
  
* Minor documentation fixes.

* 3rd party libraries BeanShell and ORO were upgraded. The upgrades fix
  a few bugs.

* Warning! Incompatible Java API change! Package fmpp.listeners were
  renamed to fmpp.progresslisteners.

* Warning! Incompatible Java API change! Engine.removeAttribue was
  renamed to Engine.removeAttribute.

-- 
Best regards,
 Daniel Dekany




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click