1 sept. 2015
Gendoc 0.5.1 available
The version 0.5.1 is available on Gendoc website: http://www.eclipse.org/gendoc/downloads/download.php
If you have 0.5.0 version installed you can perform an update of your installation.
This version improves the parsing of tags (whitespace and style problems), the usage of default bundles in fragments and fixes Sonar reported issues, you can find the whole list of fixed bugs here: https://projects.eclipse.org/projects/modeling.gendoc/releases/0.5.1/bugs
The Gendoc team
(original link of this post)
21 avr. 2015
Gendoc v0.5 released
Gendoc is a template based technology allowing generation of OpenXML (Word) and Open Document (OpenOffice, LibreOffice) documents from EMF Models/XML using Acceleo language. Gendoc is currently industrially used in several critical systems company (space, avionics).
To start working with Gendoc and Luna please find update site in downloads section : http://www.eclipse.org/gendoc/downloads/download.php
Documentation and tutorials are available here : http://www.eclipse.org/gendoc/documentation/documentation.php
For any information or questions feel free to use links referenced on community section.
13 juil. 2012
Frama-C Development Tooling (FCDT) plug-in V1.2 Release
- Bug #4063 (makefile in subdir)
- Improvement of ACSL editor in C code
- New Preferences (for Codan launching mode) Setting page with dynamic update with Frama-C features (linux only)
- Frama-C configuration (for Codan launching mode) in project properties
6 avr. 2012
TOPCASED 5.2.0 available
TOPCASED has been release this is the official mail sent to the community:
TOPCASED 5.2.0 is now available. It is based on the latest Eclipse 3.7 SR2 platform (Indigo) and requires a JRE 1.6.
You can download the RCP version, features and the release note at the following link : http://www.topcased.org/index.php?idd_projet_pere=52&Itemid=60
http://gforge.enseeiht.fr/scm/viewvc.php/releng/org.topcased.releng/topcasedBookmarks.xml?root=topcased-mm&view=markup
- Analyze and Repair Function
- Open referencing diagrams
- Implicit navigation from properties
- Todo notes
The user can configure a comment prefix tag used for the analysis :
After the configuration is done every comment starting with this tag will be recognized by the tool and displayed in the Tasks view. This is very useful for Model Review
- Configuration files for import document


- There are also some new features in Gendoc2 which will be described in a future post
16 févr. 2012
FCDT v1.1 release
We are pleased to announce the new release of the Frama-C Development Tooling (FCDT) plug-in version v1.1.
The FCDT plug-in permits developers to use the static analysis tools provided by Frama-C from directly within the Eclipse framework.
This release, compatible with Eclipse Indigo (only), includes:
- A new call graph viewer
- A new editor for ACSL language integrated into comment area of the CDT editor
- Bug fixes
Tested platforms are Windows XP 32 and Linux.
It is available on:
http://gforge.enseeiht.fr/projects/fcdt/
Release contents:
- FCDT plug-in archive file http://gforge.enseeiht.fr/frs/download.php/3592/fcdt_v1.1.zip
- Installation and usage tutorial http://gforge.enseeiht.fr/frs/download.php/3651/Tutorial_V1.1.pdf
- Example archive file http://gforge.enseeiht.fr/frs/download.php/3597/fcdt_v1.1_example_files.zip
A build of Frama-C Nitrogen for Windows is also available on the fcdt web site.
Regards
FCDT Team
29 déc. 2011
Extract relevant elements from a diagram
This feature makes possible to extract elements you desire in a diagram.
This example will generate a part of the UML Metamodel documentation.
The diagram realized with MDT Papyrus is presented bellow:
This diagram displays some information about Events, Activity Nodes and Operations. For the documentation we only want to display the elements linked to the Signal Event and the Call Event meta classes.
This is now possible using new methods in TOPCASED and GMF bundles.
This is the code to use in your gendoc2 template :
- The diagram is get using getPapyrusDiagrams() method
- A list of visibleElements is computed using a focused class (SignalEvent or Call Event)
- [let visibleElements : Set(uml::Class) = Set{focus}->union(focus.superClass)->union(focus.superClass->closure(superClass)->union(focus.getAssociations().memberEnd->select(type <> focus).type->asSet()))]
- The list of visible elements is used by the getDiagram method
- Finally the elements visible in the diagram are listed and for each element the documentation is displayed
29 nov. 2011
Open Tests : manage test campaigns inside Eclipse
Open Tests can provide the following services :
- write a test library
- reference requirements inside tests
- import requirements from TOPCASED Requirement format
- define test campaigns
- write test execution results
- access all data through customizable queries
- generate reports (Excel / PDF) all along the process
How to use OpenTests from Web client ?
see Video
How to use OpenTests inside Eclipse?
see Video
For more information about OpenTests :
see Open Tests tutorial or gPM Installer
Contacts : eclipseatos@gmail.com
or anne.haugommard@atos.net
18 nov. 2011
EclipseCon proposals
- MDT Papyrus usage in industrial context - sharing feedback with community
- This talk is a good opportunity for community to have feedbacks of industrials of MDT Papyrus usage.
- BIRT for reporting ... what about documentation ? Here comes Gendoc2 !
- BIRT everybody knows, why do we need another tool to generate documentation ? Because the task is different and industrials have of course reporting expectations but the also need a documentation compliant with the Quality Kit of the company.
- FCDT, formal proof integration in CDT using Codan and XText
- This talk will present how the CDT has been extended to provide an open source formal proof IDE using a powerful static analysis tool (Frama-C)
17 oct. 2011
TOPCASED 5.1.0 available
"Dear TOPCASED users,
TOPCASED 5.1.0 is now available. It is based on the latest Eclipse 3.7 SR1 platform (Indigo).
Note: the official announce on website is not yet present ( will be available on Monday morning) but the “download” link already targets the 5.1.0 release.
Previous TOPCASED 5.0.0 release introduced integration of Eclipse MDT papyrus editors (UML&SysmL) but those editors were not mature.
There has been a lot of work done to fix all major issues and those editors can now be considered as “usable” in TOPCASED 5.1.0.
For any new project we recommend that you have a look at those editors as they provide strong ergonomics improvements (in reference to previous TOPCASED editors), a better support of UML& SysML specification and a very good support for profile customization.
For existing models, we recommend that you continue to use former UML and SysML TOPCASED editors as there is not yet automatic transformation between former graphical format and Papyrus one. This transformation is in progress and should be available in TOPCASED 5.2.0 (planned for January).
Note: You will find two different perspectives to distinguish former and new editors for UML and SysML.
You can download the RCP version, features and the release note at the following link : http://www.topcased.org/index.php?idd_projet_pere=52&Itemid=60 and the Linux
You can also install TOPCASED 5.1.0 from the update-site : http://topcased-mm.gforge.enseeiht.fr/indigo/release/topcased5.1
You can find more information on the official TOPCASED website: http://www.topcased.org/
A new section "Indicators" has been created to show statistics on some components.
Users support: Help is available through the 'Help > Help Contents' menu of TOPCASED. However if you have any questions, you can get support through the TOPCASED Users mailing list: topcased-users@lists.gforge.enseeiht.fr To be able to use the mailing-list, don't forget to subscribe to it, first.
Developers support: You may find information on the dedicated developers page of the TOPCASED official website. If you have any questions, you can also use the TOPCASED developers mailing list and sending your questions to: topcased-devel@lists.gforge.enseeiht.fr
Report a bug: To report a bug against TOPCASED, create a new entry on our bug tracker. You need to be logged on the site to be able to create an entry. * Ask for a new feature To ask for a new feature on TOPCASED, create a new entry on our feature tracker. You need to be logged on the site to be able to create an entry.
TOPCASED Contact TOPCASED is a collaborative project: if you are interested in helping in some aspects of our technical roadmap (or in extending it), you may contact us at topcased-contact@list.gforge.enseeiht.fr Your participation is welcome. Kind regards, The TOPCASED team"
- Default documentation generation
If your model does not contain "Rich text" documentation you can right click on your model and generate the documentation - Palette Customization (stereotype application for example)
This feature allows user to create elements with specific stereotype applied, or force the user to enter values at creation ... - Requirement Traceability
Import requirements from documents and create Traceability link to UML or SysML editor - Export all diagrams
Export all the diagrams contained in a model - Advanced Label editors
label edition with auto completion for model elements (in the screenshot, properties)
3 août 2011
TOPCASED 5.0.0 available
TOPCASED 5.0.0 is now available.
It is based on the latest Eclipse 3.7 platform (Indigo), and it is the first official TOPCASED version containing MDT Papyrus. For this integration all the TOPCASED components have been adapted to support MDT Papyrus, it is now possible with MDT Papyrus to :
- generate documentation
- create Requirement traceability
- create Scripts for MDT Papyrus models
You can download the RCP version, features and the release note at the following link :
http://www.topcased.org/index.php?idd_projet_pere=52&Itemid=60
Windows, Linux and Mac OS versions are available
You can also install TOPCASED 5.0.0 from the update-site :
http://topcased-mm.gforge.enseeiht.fr/indigo/release/topcased5.0.0/
You can find more information on the official TOPCASED website :
http://www.topcased.org/
A new section "Indicators" has been created to show statistics on some components.
- Users support:
Help is available through the 'Help > Help Contents' menu of TOPCASED.
However if you have any questions, you can get support through the TOPCASED Users mailing list: topcased-users@lists.gforge.enseeiht.fr
To be able to use the mailing-list, don't forget to subscribe to it, first. - Developers support:
You may find information on the dedicated developers page of the TOPCASED official website.
If you have any questions, you can also use the TOPCASED developers mailing list and sending your questions to: topcased-devel@lists.gforge.enseeiht.fr - Report a bug:
To report a bug against TOPCASED, create a new entry on our bug tracker.
You need to be logged on the site to be able to create an entry. - Ask for a new feature
To ask for a new feature on TOPCASED, create a new entry on our feature tracker.
You need to be logged on the site to be able to create an entry. - TOPCASED Contact
TOPCASED is a collaborative project: if you are interested in helping in some aspects of our technical roadmap (or in extending it), you may contact us at topcased-contact@list.gforge.enseeiht.fr
Your participation is welcome.
16 juin 2011
Gendoc2 : New attribute to simplify debug
With next version of Gendoc2 (TOPCASED 5.0.0, July 2011), you can add an “Id” into each gendoc tags as an attribute.
It identifies the tag in the document, and allows tracing an error on the tag where it is declared in order to makes debugging easier. It captures most of the errors that can occur in a script. The ID can trace the following errors:
- Incomplete tags
- Script error
- Image not executed
- Configuration error
How to use ids?
The ID is used by writing the keyword “id” that assigns a string (of course between simple quotes) like this: <gendoc id='my id' >...</gendoc>
If during generation an error is found in one tag, its id will appear in the details of the warning message. Here are some screenshots to explain this:
The resulting error message allows to identify exactly which tag is in error:







