Updating Draw.io (Diagrams.net)

98 views
Skip to first unread message

gah...@gmail.com

unread,
Aug 1, 2020, 1:40:55 PM8/1/20
to Sandstorm Development
I was hoping that there would be an updated draw.io app soon with the recent resurgence.  However, in looking at what it might take to start on such a thing, I found that it looks like draw.io, now diagrams.net, has moved to a docker install process.  Is it a correct assumption that this is going to make an upgrade of the app major, if even possible?  There's some pretty big feature updates in the newer version, especially in regards to linking between objects and pages.  At one point there was also a "chip-in" page where someone could pledge a certain amount towards things like upgrading an app.  I'm unable to find that now.

Jacob Weisz

unread,
Aug 1, 2020, 2:02:53 PM8/1/20
to sandst...@googlegroups.com
I am not sure what breaking changes they may have made, but I doubt it's super difficult. Draw.io paid someone to update it last time they updated it, but I imagine they haven't gotten enough requests for it to maintain it.

You'd also probably need to go back to the last version with Sandstorm in the source tree to get the build files they've since deleted, if I recall. But you could add them back and see how much is broken and if it can be built.

If someone got an updated package working, I imagine they would be happy to publish it. But I doubt they want to spend significant money/time working on it.

--
  Jacob Weisz



On Fri, Jul 24, 2020, at 2:32 PM, gah...@gmail.com wrote:
I was hoping that there would be an updated draw.io app soon with the recent resurgence.  However, in looking at what it might take to start on such a thing, I found that it looks like draw.io, now diagrams.net, has moved to a docker install process.  Is it a correct assumption that this is going to make an upgrade of the app major, if even possible?  There's some pretty big feature updates in the newer version, especially in regards to linking between objects and pages.  At one point there was also a "chip-in" page where someone could pledge a certain amount towards things like upgrading an app.  I'm unable to find that now.


--
You received this message because you are subscribed to the Google Groups "Sandstorm Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sandstorm-de...@googlegroups.com.

Greg Harris

unread,
Aug 5, 2020, 11:55:49 AM8/5/20
to Jacob Weisz, sandst...@googlegroups.com
Hrm.  Kind of what I was expecting even if I was hoping otherwise.  I’ll have to make some decisions before jumping into this one headlong, so don’t be expecting anything soon.

Thanks.

You received this message because you are subscribed to a topic in the Google Groups "Sandstorm Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sandstorm-dev/OIseYP24pBI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sandstorm-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sandstorm-dev/022521a3-7deb-4f39-a4bf-dee15f819c96%40www.fastmail.com.

David Benson

unread,
Aug 25, 2020, 6:30:47 AM8/25/20
to Sandstorm Development
We can add the sandstorm build files back in, if someone wants to try them, they'll go under /etc/sandstorm on the next release. https://github.com/jgraph/drawio

You don't use the docker version, the sandstorm build is the client only communicating directly against the API, it doesn't use the bridge thingie.

Is transferring the release keys to you, Jacob, an option? Given our lack of updating, it's better someone on the SS project has control of the releases.

Jacob Weisz

unread,
Aug 25, 2020, 11:45:37 AM8/25/20
to sandst...@googlegroups.com
There is probably a growing "if Jake ever becomes evil" problem for release keys... but yeah, I can probably take a pass at putting together a release. I know you've had a lot of releases/updates since our last Sandstorm version, so the benefits are probably decent, and it'd be good to update the branding in the package metadata in addition to preventing that client-side loading we discussed on the GitHub issue.

--
  Jacob Weisz

Reply all
Reply to author
Forward
0 new messages