Difference between revisions of "Protege 4.2 Beta Release Notes"

From Protege Wiki
Jump to: navigation, search
Line 11: Line 11:
  
 
The contents of the release notes section describe changes relative to Protege 4.1 and Protege 4.2 alpha.
 
The contents of the release notes section describe changes relative to Protege 4.1 and Protege 4.2 alpha.
 +
 +
=== Build 275 -- May 21, 2012 ===
 +
 +
* Fixed a bug in the [[OWLViz|OWLViz]] visualization plug-in that caused NumberFormatExceptions.
  
 
=== Build 274 -- May 18, 2012 ===
 
=== Build 274 -- May 18, 2012 ===

Revision as of 18:09, May 21, 2012


Protege 4.2 Beta

Screenshot of Java code generation - new in Protege 4.2 beta!

We are pleased to announce Protege 4.2 beta! The main thrust of the 4.2 series will be the roll out of several new plug-ins, including an ontology difference tool, enhanced explanation support, client-server capabilities, support for code generation, and a database back-end. Please contact us via the Protege 4 mailing list with questions, feedback, and bug reports.

Download Protege 4.2 beta from the main Protege website (new users, please register first).


Release Notes

The contents of the release notes section describe changes relative to Protege 4.1 and Protege 4.2 alpha.

Build 275 -- May 21, 2012

  • Fixed a bug in the OWLViz visualization plug-in that caused NumberFormatExceptions.

Build 274 -- May 18, 2012

  • Fixed several bugs in the OntoGraf visualization plug-in that caused ClassCastExceptions.

Build 273 -- May 11, 2012

  • It is now possible for users to download and/or update plug-ins even when the Protege distribution is read-only. If the auto update mechanism can't write to Protege's plugin subdirectory, it falls back to writing to a user directory. This mainly effects Windows users who install to the Program Files directory, but it's also important for Linux administrators who create a shared Protege installation for multiple users.
  • Modified the annotation editor so that it remembers which tab was last selected.
  • Deprecated entities now get rendered with strikethroughs.
  • The button for editing annotations on axioms now gets highlighted in orange when an axiom has annotations, thus making it easier to notice.
  • Fixed a bug in the ontology repository mechanism that caused some valid XML catalog files to be rejected.
  • Fixed a bug that caused the save operation to add extra axioms from imported to importing ontologies.
  • Fixed a bug where automatically generated IDs would get incremented on each keystroke when users created new entities.
  • Fixed a long-standing bug where Protege would freeze while trying to generate a new ID for an entity.
  • Fixed a bug in the Bookmarks plug-in that caused it to fail immediately upon being activated in the user interface. The Bookmarks plug-in is available for download via the auto update mechanism (File | Check for plugins... | Downloads | Bookmark View).
  • Fixed a bug in the OWLDoc plug-in where clicking on the Show Source button caused a NullPointerException. The OWLDoc plug-in is available for download via the auto update mechanism (File | Check for plugins... | Downloads | OWLDoc).

Build 269 -- March 21, 2012

  • Introduced a new explanation plug-in in addition to the existing basic explanation plug-in provided in previous releases. The new explanation plug-in, referred to as "Justification Based Explanation", will generate multiple explanations for a single inference, will sort the explanation to be more readable, and can generate laconic explanations (laconic justifications). The plug-in can also generate explanations for inconsistent ontologies (previous releases only included an ad-hoc tool, which in some cases was unable to find any explanation for a problem).
  • Fixed a bug that could cause Protege to crash during start-up.

Build 265 -- March 14, 2012

  • Improved the user interface for the Active Ontology tab so that the ontology name and version are much more prominent, thereby encouraging users to set versions when appropriate.
  • Launching the Protege application now opens an empty ontology instead of a welcome screen. This is part of a broader effort to align Protege's behavior with common document editing tools, e.g., opening Microsoft Word presents users with a blank document.
  • Added support for Java code generation. Available from Tools | Generate Protege-OWL Java Code.
  • Protege no longer requires administrative privileges to run on Windows machines. Please note the exception that downloading new plug-ins will still require Protege to be run in administrative mode.