Rodin Platform 2.2 Release Notes: Difference between revisions

From Event-B
Jump to navigationJump to search
← Older editNewer edit →
imported>Nicolas
imported>Nicolas
Line 3: Line 3:
== What's New in Rodin X.X? ==
== What's New in Rodin X.X? ==
* General Interface
* General Interface
{{TODO | ...}}
:'''Improved general platform performance.''' The build time has been decreased by about 40% on average since Rodin 2.0.
:See: [[Rodin Performances]]


* Modelling
* Modelling
{{TODO | ...}}
:{{TODO}}


* Proving
* Proving
{{TODO | ...}}
:'''New Tactics''',  such as ''Negation Normal Form'', ''Generalized Modus Ponens'', ''Case distinction from implication''.
:* Comments on the proof tree
:* Parenthesis highlighting in hypotheses and goal
:* Find/Highlight in hypotheses and goal


* Changes for plugin-developers
* Changes for plugin-developers
{{TODO | ...}}
:'''Proof storage''' has evolved with backward compatibility: it is transparent for common proof access (getting the proof tree/skeleton). However, for a plug-in that would access proofs using directly the database - which is highly discouraged, please note that IPRProofRule.getElementName() does no more contain a reasoner id, but instead a reference to a IPRReasoner, a newly introduced proof element type. See [[Proof Dependencies and Reasoner Conflicts]].
:* Proof storage has evolved with backward compatibility: it is transparent for common proof access (getting the proof tree/skeleton). However, for a plug-in that would access proofs using directly the database - which is highly discouraged, please note that IPRProofRule.getElementName() does no more contain a reasoner id, but instead a reference to a IPRReasoner, a newly introduced proof element type. See [[Proof Storage]] {{TODO}}.
:* '''Signature''': optionally, a reasoner may now implement the interface '''ISignatureReasoner'''. It is designed for those whose behaviour evolves during a session. A signature represents a single reasoner behaviour. When present, the signature is stored in proofs. These proofs are invalidated when the signature changes (detected at build time).
:* External plug-ins can now contribute to the "Refine" action which produces a new component from an existing one.
:* External plug-ins can now contribute to the "Refine" action which produces a new component from an existing one. It replaces the former non extensible actions ''Refine'' and ''Extend''.
 
* Invisible but noteworthy changes
:* to improve performance of proof status computation, proof storing has evolved, in a transparent and backward compatible way (see [[Proof Dependencies and Reasoner Conflicts]]).


== Requirements ==
== Requirements ==

Revision as of 12:55, 1 June 2011

What's New in Rodin X.X?

  • General Interface
Improved general platform performance. The build time has been decreased by about 40% on average since Rodin 2.0.
See: Rodin Performances
  • Modelling
TODO
  • Proving
New Tactics, such as Negation Normal Form, Generalized Modus Ponens, Case distinction from implication.
  • Changes for plugin-developers
Proof storage has evolved with backward compatibility: it is transparent for common proof access (getting the proof tree/skeleton). However, for a plug-in that would access proofs using directly the database - which is highly discouraged, please note that IPRProofRule.getElementName() does no more contain a reasoner id, but instead a reference to a IPRReasoner, a newly introduced proof element type. See Proof Dependencies and Reasoner Conflicts.
  • Signature: optionally, a reasoner may now implement the interface ISignatureReasoner. It is designed for those whose behaviour evolves during a session. A signature represents a single reasoner behaviour. When present, the signature is stored in proofs. These proofs are invalidated when the signature changes (detected at build time).
  • External plug-ins can now contribute to the "Refine" action which produces a new component from an existing one. It replaces the former non extensible actions Refine and Extend.

Requirements

TODO: COPY REQUIREMENTS FROM PREVIOUS PAGES / VERIFY
TODO: Inform here of some specific system requirements (version of Java, etc).

  • Linux: the internal browser does not work with xulrunner-2.0 (for instance, it causes the welcome page to display a link instead of a html page); xulrunner-1.9.x must be installed.

Installing

Upgrading from Rodin 2.1.x

Use rodin-2.2-repo.zip, check "contact all update sites" (because a new version of Eclipse is used).

Downloading

TODO: Add here a link to download the platform.

External plug-ins

TODO: Link to the external page for plug-ins
Link of the form: 

{{:Rodin_Platform_2.2_External_Plug-ins}}

Fixed Bugs

TODO: Add here a list of the fixed bugs.

Known Issues

TODO: COPY KNOWN ISSUES FROM PREVIOUS PAGES / VERIFY
TODO: Add here a link to the SourceForge Bugs page, after filtering bugs (Assignee Any, Status Open, Category Any, Group 1.2).

Disclaimer

Since Rodin is continuously maintained, several unsoundness bugs which have been encountered were investigated and fixed. However, despite the total commitment of our teams to insure the soundness of the platform, some unexpected and unknown soundness issues could remain. We would be grateful if you would report these issues to the development mailing list.

About

Rodin Platform up to r11814

Developer Release date : 01/06/2011.

User Release date : 03/06/2011.

Retrieved from ‘https://wiki.event-b.org/index.php?title=Rodin_Platform_2.2_Release_Notes&oldid=7705’