Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't wait to see this work with my existing .ysc files #3

Open
winzkigermany opened this issue Dec 11, 2024 · 2 comments
Open

Can't wait to see this work with my existing .ysc files #3

winzkigermany opened this issue Dec 11, 2024 · 2 comments
Labels
question Further information is requested

Comments

@winzkigermany
Copy link

Will there be a migration path?

@terfloth
Copy link

@winzkigermany - thank you for the first issue! :-)

Yes - there will be a way to use Eclipse-style .ysc (and .sct) models in VSCode (and likely vice versa). Currently you can convert .ysc models into .scm via the cloud editor:

  1. open the cloud editor at https://create.itemis.io (sign up required)
  2. Select 'Folder (Symbol) > New Cloud Statechart > Import Local File' from tool bar and select your .ysc.
  3. The converted statechart should appear.
  4. Select 'Convert to Local Statechart (diskette/save symbol)' from toolbar (only with Chrome & Edge browsers)
  5. alternatively select 'Export Statechart (download symbol) > Export Statechart' from tool bar to save it to the downloads folder

Of course this is a kind of detour and will be more tightly integrated. Please be also aware that the conversion from .ysc to .scm is not complete yet. The diagram requires you to manually fix the layout and some features like sub diagrams are not supported yet.

@terfloth terfloth added the question Further information is requested label Dec 12, 2024
@winzkigermany
Copy link
Author

Okay, I've tried the steps so far, and after manually removing "modelId", and the surrounding "graph" and the complete "genModel" section from the scm file, I am now at least able to see the vscode plugin showing the graphs (and I can edit them).
Of course I would need to rearrange everything, but that's a minor inconvenience, and could be done in some hours.
So far, this looks promising, keep up the good work!

I won't be able to go on testing until there is a way to integrate sub diagrams (a workaround would also be fine for me, for example extracting them into the surrounding diagram) and doing imports for multi-state-machines, and of course integration/includes of c code... I'll simply breathe down your necks while you implement the missing features ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants