|Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] lRE: User Experience with papyrus|
as Sebastien said, zipping is very likely not the problem, but
rather reopening a saved model. If there is an exception during
save, one of the three files is eventually only partially written.
We could examine this, if you share the three files of a corrupted
model (e.g. by private mail to Sebastien or me).
This problem happened to me in case of a model that applied a
specific profile. In my case, the culprit was a derived attribute
in this profile which had a bad implementation that could
eventually throw an NPE (i.e. not an issue in Papyrus core).
Thanks for the details.
In practice, papyrus models are made of 3 complementary files, with .di, .notation and .uml extensions.
All of them should be shared with colleagues. The corruption error you report typically occurs when only the .di file is shared (but there can be other reasons).
Did you include the .notation and .uml in your zip?
It’s really hard for me to figure out how a zip export could have modified the original file.
But unfortunately Sequence Diagram is known to be unstable, and maybe an explanation can be that the steps: saving -> closing papyrus editor (not necessarily eclipse)-> reopening papyrus model led to a layout corruption (which is, I agree, a pity).
We will do our best to improve our tool stability (with the resources we manage to have as an Open Source project). Maybe some of my colleagues will ask you for more details on the actions you did with the sequence diagram editors.
In the meantime, and to avoid too much inconvenience, I would recommend you to very frequently save your work and get the benefits of the built-in “Local History” feature provided by Eclipse.
If at some point you are in a situation where you can’t undo a modification in the editor, close your papyrus model, right click on the “.notation” file -> Replace With -> Local History (see screenshot  below).
It will allow you to restore a previously saved version of your file.
Depending on the kind of change you did, you may have to do the same with the .uml file : the .notation file contains info about the diagrams and their layouts, whereas the .uml file contains the semantic info about the elements displayed (or not) in the diagrams (the model tree you can see in the model explorer).
For instance, if you move and existing class in a diagram, only the notation will be impacted. If you rename it, only the .uml will be changed. If you a delete it, or create a new one, both are impacted…
The .di file generally contains very few information and doesn’t change frequently.
I hope it helps,
Sebastien on behalf of the CEA Papyrus Team.
De : mdt-papyrus.dev <mdt-papyrus.dev-bounces@xxxxxxxxxxx> De la part de Ina Borisova
Envoyé : jeudi 8 avril 2021 19:21
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] User Experience with papyrus
Thank you for your immediate replies, I honestly did not expect any!
I will upload a word file with all the information copied from the configuration log and the different ways my sequence diagram changed while making it as well as what I did or tried to do last before it changed because papyrus froze and I couldn't undo moving an element or creating another.And how the diagram changed after I zipped it. I fortunately did not receive a corruption error so I can only include a screenshot of the message take from one of my coursemates.
Thank you once again for taking notice in my feedback.
PS: I am using Mac OS BigSur and papyrus version: 22.214.171.124012091059
On Thu, 8 Apr 2021 at 15:23, RADERMACHER Ansgar <Ansgar.RADERMACHER@xxxxxx> wrote:
I'm sorry that you had such a bad experience with Papyrus. Can you please tell us which version of Papyrus you are using on which OS? While there are some issues (e.g. in the Sequence diagrams), corruption of model files hasn't happened in my usage for a very long time.
As Ed has already said, it would be great if you can describe the step to reproduce a bug so that we can examine what happens. If you have a corrupted model file you can eventually share it so that we can examine what went wrong.
(on behalf of the CEA Papyrus team).
From: mdt-papyrus.dev [mdt-papyrus.dev-bounces@xxxxxxxxxxx] on behalf of Ina Borisova [ina.a.borisova@xxxxxxxxx]
Sent: Thursday, April 08, 2021 01:51
Subject: [mdt-papyrus.dev] User Experience with papyrus
My name is Ina and I am writing to you to share my experience using papyrus.
I am a student at Kings College London and for a coursework project we were required to use papyrus to create use case diagrams, class diagrams, state machines and sequence diagram. My course has 3-4 hundred students and each one of us had constantly issues with the software receiving errors saying "Your file is corrupted" and diagrams being deleted for no apparent reason, the software freezing and modifying the diagrams on its own. I do not feel like Papyrus is a proper tool for project management as it constantly ruins projects and does not in any way assist the work.
I have had to re-do one sequence diagram 5 times because papyrus froze and didn't allow me to create, change or delete anything, and if it did allow it, it wouldn't display it on the diagram. When I actually managed to created the aforementioned diagram on the 5th attempt, 9 hours later, AND MIND YOU IT WASN'T A COMPLEX OR LONG ONE, I zipped the file and send it to my team.
Now imagine my surprise when I looked at the report, containing screenshots of the diagram, and saw that the ONE diagram which had been tormenting me for 9 HOURS STRAIGHT HAD CHANGED WITHOUT ME DOING ANYTHING TO IT. This wouldn't have been a problem had my original file not changed as well after the zipping, nor if papyrus had allowed us to change it back to how it was originally. The software wouldn't allow us to select anything inside the fragments, move or rename elements. And it was not only so for one device.
One of my team mates had three of her diagrams deleted because papyrus decided out of no where that the files are corrupted. And what exactly does it mean corrupted!?
This project is worth 20% of the final mark for the module for 6 people in my team and another 60 teams of 5 to 6 people.
Finishing this project has been a torment because of every issue with Papyrus and trying over and over again to create something just to watch your effort go down the drain is emotionally and physically tiring. I am not in the slightest satisfied with your software and if was given the choiceI would have immediately transferred to "Visual Paradigm" which is a tool that my team and I used to create our sequence diagrams and didn't have one single issue with. But the coursework requires us to use Papyrus so transferring our not at all complex or long 9 diagrams manually to papyrus has taken us longer than actually creating them and has exhausted us twice as much.
I really hope you take this rather harsh feedback and improve the software because I do suppose that we will be using it again next year and I do not want to write the same email again.
Thank you for reading my feedback and for your time and patience to finish this email.
Ina on behalf of all 3-4 hundred students in Kings College London.
mdt-papyrus.dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev
Back to the top