CamilleX User Guide: Difference between revisions

From Event-B
Jump to navigationJump to search
imported>Son
No edit summary
imported>Son
No edit summary
Line 10: Line 10:
=== Setup ===
=== Setup ===


* Before install the Event-B XText front-end, you need to add the XText update site (http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/) as an additional software site.
* Before install XEvent-B, you need to add the XText update site (http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/) as an additional software site.
* The Event-B XText front-end is available as a separate plug-in from the main Rodin update site (under 'Editors' category)
* XEvent-B is available as a separate plug-in from the main Rodin update site (under ''Modelling Extensions'' category)


=== Release Notes ===
=== Release Notes ===
See [[Event-B_XText_Front-end_Release_Notes | Event-B XText Front-end Release Notes]]
See [[XEvent-B_Release_Notes | XEvent-B Release Notes]]


=== IMPORTANT ===
=== IMPORTANT ===
* Currently, Event-B XText front-end ONLY supports "standard" Event-B machines and contexts.
* Currently, XEvent-B supports "standard" Event-B machines and contexts and machine inclusion/event synchronisation mechanisms.
* Since the XContexts and XMachines are compiled to the Rodin files, the corresponding Rodin contexts and machines will be '''OVER-WRITTEN'''. Any changes in the Rodin files will not be lost.
* Since the XContexts and XMachines are compiled to the Rodin files, the corresponding Rodin contexts and machines will be '''OVER-WRITTEN'''. Any changes in the Rodin files will not be lost.
* '''DO NOT USE''' the Event-B XText Front-end if you use modelling plug-ins such as iUML-B state-machines and class-diagrams, as the additional modelling elements will be over-written.
* '''DO NOT USE''' XEvent-B if you use modelling extensions such as iUML-B state-machines and class-diagrams, as the additional modelling elements will be over-written.
* Windows users '''must''' change the workspace text file encoding to '''UTF-8'''. This can be updated under the Rodin Preferences: General/Workspace then in the ''Text file encoding'' section, select Other: ''UTF-8''.


=== KNOWN ISSUES ===
=== KNOWN ISSUES ===
- Converting to XText: Currently, the "extended" attribute of events are not serialised.
- Converting to XText: Currently, the "extended" attribute of events are not serialised.

Revision as of 07:40, 22 July 2017

The complete XEvent-B User Guide is available as pdf here. Some important information is listed below.

Introduction

The Event-B XText front-end provides text editors for XContexts and and XMachines which then compiled automatically to Event-B contexts and machines.
For more details about the principles of this editor, see the XEvent-B page.

Installation

Setup

Release Notes

See XEvent-B Release Notes

IMPORTANT

  • Currently, XEvent-B supports "standard" Event-B machines and contexts and machine inclusion/event synchronisation mechanisms.
  • Since the XContexts and XMachines are compiled to the Rodin files, the corresponding Rodin contexts and machines will be OVER-WRITTEN. Any changes in the Rodin files will not be lost.
  • DO NOT USE XEvent-B if you use modelling extensions such as iUML-B state-machines and class-diagrams, as the additional modelling elements will be over-written.
  • Windows users must change the workspace text file encoding to UTF-8. This can be updated under the Rodin Preferences: General/Workspace then in the Text file encoding section, select Other: UTF-8.

KNOWN ISSUES

- Converting to XText: Currently, the "extended" attribute of events are not serialised.