-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Diagraming in gitpod? #1299
Comments
@Kreyren I know that several projects are using Sprotty to generate diagrams in Gitpod. Also, I remember a JS implementation of Dot, and there is also https://github.com/tpatel/OpenSequenceDiagrams.js/ for sequence diagrams. There are probably more diagramming libraries that could work well in Gitpod. :) (Actually even Dot itself now that I think of it.) |
@jankeromnes Sprotty is perfect! Thanks!! ^-^ In theory i can also use it to generate a dependency graph for packages o.o Is there any configuration for sprotty to run in gitpod? (So that i can develop the diagrams on it) |
solved |
@Kreyren It seems that the Sprotty repo is itself configured for Gitpod: https://github.com/eclipse/sprotty Not sure if that answers your question though. If not, could you please clarify? Also, happy diagram-making! 📊 🥳 |
yep i was blind and missed it 😄 |
Reopening, it turned out that i am incompetent eclipse-sprotty/sprotty#166 or sprotty configuration for theia is outdated and i do not know how to update it >.> EDIT: in theory i do know how, but having a confirmation on the issue so that i am not fixing working thing would be appreciated. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Referencing https://github.com/RXT0112/Zernit/issues/59 for requirement tracking
I am a have hard time finding a diagramming tool that plays well with gitpod.
Can you recommend me some so that i wouldn't have to make one from scratch? ^-^
The text was updated successfully, but these errors were encountered: