Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Exporting textual representation of a statechart

30 views
Skip to first unread message

Aivar Annamaa

unread,
Jun 30, 2021, 6:04:45 AM6/30/21
to YAKINDU User
Hi!

Does Yakindu allow exporting a model into some kind of human-readable textual format for easy diffing and searching? 

I'm aware of the diff feature in the Eclipse plug-in, but IMO it is not very easy to use. I'm thinking of a workflow, where the developer, after making changes to a model, commits sct files together with regenerated textual representations, so that the other developers in the team don't need to fire up Eclipse to spot the changes.

If this feature doesn't exist yet, then do you think it's feasible to transform sct files into a human-readable format? Do you know an existing format, which could be suitable target for Yakindu's models? Perhaps Sismic (https://sismic.readthedocs.io/en/latest/)? Something else?

Best regards,
Aivar



Andreas Mülder

unread,
Jun 30, 2021, 1:57:41 PM6/30/21
to YAKINDU User
Hi Aivar,
this feature does not exist yet. 
However, transforming the model into a more readable format is not a big thing. For example, we have an SCXML Code Generator. It is still XML format, but way more readable than our internal XMI format.
If you want to have a look, here are some examples: https://github.com/Yakindu/scxml-examples
Also a sismic generator would be possible. The main problem is, that you can't use such a format for diff and merge, because it only contains the state machine, but not the statechart. All the things that are stored in the notation model
like layout, bounds, colors, fonts, sizes, and the like would be lost when working on such a model.

Best regards,

Andreas
Reply all
Reply to author
Forward
0 new messages