Back in June, I reported that a new variant of Papyrus was being funded for development by the Papyrus Industry Consortium.
Well there’s no turning back with an official article in this month’s Eclipse Newsletter!
It had to happen: Papyrus is now available at version 4.0! That’s Papyrus “Photon” for those of you who follow the Eclipse release names.
Curious about what was done in this release? You can find that in the list of addressed issues (a.k.a., the bug list). The following topics are addressed:
Want to try it out? Here are a few links to help you:
(* In case you were wondering, “RCP” stands for “Rich Client Platform 😉
Good news! The Papyrus Industry Consortium’s steering committee has approved the creation of a “Papyrus UML Light” addition to the product line!
My insiders have been telling me that work is ongoing on the requirements for this new tool.
Would you like to have a voice? Well you can do so through the Papyrus IC public Tuleap repo’s product management forum! (You may remember my previous post about Tuleap).
In this context, the Papyrus development team is putting together a “Papyrus coding day” just before EclipseCon France.
During this free coding day, they will provide you with:
Registration is mandatory as there is a limit on the number of attendees is limited.
And rejoice in that attendance is free (and includes coffee and snacks)!
There are, however, prerequisites:
So whether you are already invested in Papyrus, just curious, a toolsmith or a hacker, this may be of interest to you!
You can contact me is this is of interest and I will put you in touch with the organizers!
I received an interesting email today. Someone asked why the logo contained a flamingo!
Well, that my image is that of an Ibis, not a flamingo!
An Ibis a bird that is found in Egypt, where papyrus was used as paper (or even computers nowadays). That, and the Egyptian god Toth was often depicted as a man with the head of an ibis (I’ll let you make the link between that an me… 😉 )…
Well, I hope this clarifies that for everyone!
The sessions lineup for EclipseCon France 2018 have been published! If you plan on attending, I have a couple of suggestions for you!
First, a session about me (of course) and more love for my toolsmiths:
by Philip Langer (EclipseSource Services GmbH).
Model-based engineering tools are most successful, if they are as domain-specific as possible, reflecting the specific needs of the domain and its users. Thus, not only a domain-specific modeling language, but also a specialized modeling environment is required that takes the domain users’ background, their roles, and currently used infrastructure into account. Often, the domain-specific modeling languages have a considerable overlap with UML though.
The second session is not directly focused on me, but it is very relevant to using me as a platform for domain-specific tools (and again, more love for my toolsmiths):
by Laurent Delaigue (Obeo) and Philip Langer (EclipseSource Services GmbH)
Have you ever needed to compare and merge heterogeneous domain-specific models (with both textual and graphical syntaxes)? Or maybe you needed to review changes on graphical models? We did.
Did I miss a presentation? If so, let me know!
Today, my minions added a new page to the the unsung heroes of me: The Toolsmiths!
They are those who are brave enough to add capabilities to Papyrus and even to build new modeling tools on top of the Papyrus platform!
They are, of course, all the main developers of the Papyrus modeling platform and the various products in the Papyrus product line, but also those who provide fixes through bugzilla, those who build add-ons to Papyrus, and those who use Papyrus as the base for their own domain/company-specific modeling tools.
Interested in joining this fearless bunch? The Toolsmith page is for you!
Are you interested in writing for this blog? Please let us know!
Here are the three projects (communities) that have been created along with their descriptions, taken from each project:
|This project is the Papyrus IC’s way of openly managing the Papyrus projects and products This is our way of informing the Papyrus community about what we are doing and, in return, to get feedback from the Papyrus community. This is a source of information for the community and by the community — this is your community!|| This project is where the Papyrus product line management lives. This is where we do the nitty-gritty work so that you can enjoy our fabulous Papyrus-based products. Unfortunately, most of what we do here can be boring, day-to-day stuff, and we want our developers, designers, and managers to keep their focus, so we keep them in a quiet, private area.
But don’t worry, any significant news, decision, development, etc. Will be made available in the Papyrus IC project!
|This project is to help the Papyrus Industry Consortium’s Steering community to manage the consortium projects, products, and assets. This project is private to protect confidential information (e.g., user and supplier confidential information, financial information)
But don’t worry, Steering committee information for public consumption will be provided in the Papyrus-IC project!
My minions are still working at the governance of the projects and at transferring information from the Papyrus IC Steering into the other projects (especially to Papyrus-IC), so please be patient with them!
You can read more about this on their announcement page!
Note that they only index my semantic model (i.e., the “.uml” files) and not the diagrams, which makes sense in their context given that diagrams are not semantic elements.
Still, this is so cool!
The Papyrus layers functionality has been in incubation for a while, and some may be wondering what it’s all about:
The Layers mechanism allows to build different views of an underlying UML diagrams by applying selections rules as well as graphical transformation operators.
You can read the description of this function in the Papyrus Wiki, and you can also see it in action in this YouTube video: