Current Developments: Difference between revisions

From Event-B
Jump to navigationJump to search
imported>Mathieu
m Addition of an AnimB section, to be filled in by Christophe
imported>Mathieu
Line 22: Line 22:
;Collecting history
;Collecting history
:The history of the animation will be collected.
:The history of the animation will be collected.
[[Category:Design]]
 
[[Category:Work in progress]]

Revision as of 12:17, 18 September 2008

This page sum up the known developments that are being done around or for the Rodin platform. Please contributes informations about your own development to keep the community informed

Deploy tasks

The following tasks were planned at some stage of the Deploy project.

Rodin Index

For more details on Rodin index design, see Rodin Index Design.

The purpose of the Rodin index manager is to store in a uniform way the entities that are declared in the database together with their occurrences. This central repository of declarations and occurrences will allow for fast implementations of various refactoring mechanisms (such as renaming) and support for searching models or browsing them.

Exploratory tasks

One single View

For more details on Single View Design, see Single View Design.

The goal of this project is to present everything in a single view in Rodin. So the user won't have to switch perspectives.


Others

AnimB

For more details on AnimB Current Developments, see AnimB Current Developments.

The current developments around the AnimB plug-in encompass the following topics:

Live animation update
where the modification of the animated event-B model is instantaneously taken into account by the animator, without the need to restart the animation.
Collecting history
The history of the animation will be collected.