About
drawio-desktop is a diagramming and whiteboarding desktop app based on Electron that wraps the core draw.io editor.
Download built binaries from the releases section.
Security
draw.io Desktop is designed to be completely isolated from the Internet, apart from the update process. This checks github.com at startup for a newer version and downloads it from an AWS S3 bucket owned by Github. All JavaScript files are self-contained, the Content Security Policy forbids running remotely loaded JavaScript.
No diagram data is ever sent externally, nor do we send any analytics about app usage externally. This means certain functionality for which we do not have a JavaScript implementation do not work in the Desktop build, namely .vsd and Gliffy import.
Developing
draw.io is a git submodule of drawio-desktop. To get both you need to clone recursively:
git clone --recursive https://github.com/jgraph/drawio-desktop.git
To run this:
npm install(in the root directory of this repo)npm install(in the drawio directory of this repodrawio/src/main/webapp)- export DRAWIO_ENV=dev if you want to develop/debug in dev mode.
npm startin the root directory of this repo runs the app.
To release:
- Update the draw.io sub-module and push the change. Add version tag before pushing to origin.
- Wait for the builds to complete (https://travis-ci.org/jgraph/drawio-desktop and https://ci.appveyor.com/project/davidjgraph/drawio-desktop)
- Go to https://github.com/jgraph/drawio-desktop/releases, edit the preview release.
- Download the windows exe and windows portable, sign them using
signtool sign /a /tr http://rfc3161timestamp.globalsign.com/advanced /td SHA256 c:/path/to/your/file.exe - Re-upload signed file as
draw.io-windows-installer-x.y.z.exeanddraw.io-windows-no-installer-x.y.z.exe - Add release notes
- Publish release
Note: In Windows release, when using both x64 and is32 as arch, the result is one big file with both archs. This is why we split them.
Open-source, not open-contribution
Similar to SQLite, diagrams.net is open source but closed to contributions.
The level of complexity of this project means that even simple changes can break a lot of other moving parts. The amount of testing required is far more than it first seems. If we were to receive a PR, we'd have to basically throw it away and write it how we want it to be implemented.
We are grateful for community involvement, bug reports, & feature requests. We do not wish to come off as anything but welcoming, however, we've made the decision to keep this project closed to contributions for the long term viability of the project.