There were already a few posts [here] and [here] in which we talked about the new Papyrus UMLLight variant. Well – it is one step closer to completion.
My sources tell me that the scope has been defined and that requirements have been written, and that a request for quotation has been created and will soon be published!
UPDATE: The scope should be similar to of OMG’s OCUP2 Foundation level content.
Stay tuned for more information through official channels!
And of course, you will know about it here!
Adocus, a member of my industrial consortium, has released a version of MetaModelAgent, their DSML tool, for my Photon edition!
You can read more bout it on their release page!
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:
- A new preference has been introduced to keep stereotype application with their base element see StereotypeApplication Preference
- The hyperlink navigation has changed see Hyperlink Navigation
- Add a preference page to configure the visualization of external decorator see External Decorator
- Add auto-completion to select the type in the property view see Auto complete type
- Add an export to HTML to see model without papyrus see HTML Export
- Development and adaptation of the Layer tool for the diagrams Layers .
- Synchronization with ELK see ELK adaptation
- Tables improvements:
- display of a string instead of N/A
- Matrix improvements
- save by UUID not the positon
- Diagrams improvements:
- some problems about the name label of ports have been fixed
- some resize action in the class diagram have been fixed.
- sequence diagram – Better movement management of Elements, introduction of combined fragment, RCPTT tests.
- Integrate a tool to adapt your model based on the modification of the profile
- Architecture framework : stabilization (easier customizations/modifications by the users) and bug corrections
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 previous posts (here and here), I mentioned the increased focus on Papyrus Toolsmiths.
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:
- Hands-on sessions to get an insight on Papyrus SDK capabilities
- Discussions with the Papyrus development team
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:
- Knowledge of Java (at least intermediate level)
- EMF and UML experience is an plus!
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!
(The information you provide will only be used to put you in touch with the organizer and then deleted)
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 Mondo Project‘s mondo-hawk now supports my models!
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:
Yesterday, my minion Maximilian went to the Automotive Software Development Conference (Euroforum) and presented me and my Industry Consortium!
I hope I made a good impression (I’m sure Maximilian did a great job)!
Maybe one day, you will be driving a car with software designed with my help!
Thanks to my Minion Sébastien for pointing this out:
System modelling in AMASS with Papyrus
If you work with Cyber-Physical Systems (CPS) and do not know about AMASS, I invite you to have a look at their objectives.
This is another great example of the strength of the Papyrus solution, especially when mixed with other Eclipse and PolarSys solutions!