Go to file
mcyph 1835e6429d started integrating more examples into the next.js app 2021-03-25 12:55:45 +11:00
.github Update stale.yml 2020-11-09 20:50:48 +00:00
docs large batch convert `var` to `let` 2021-03-21 12:24:29 +11:00
src started integrating more examples into the next.js app 2021-03-25 12:55:45 +11:00
.gitignore started adding basic next.js examples app to src subdir 2021-03-21 13:00:55 +11:00
.npmignore Update .npmignore 2020-01-13 12:52:04 +03:00
ChangeLog 4.2.2 release 2020-10-28 16:11:03 +00:00
LICENSE Update LICENSE 2020-11-09 21:40:16 +00:00
README.md Update README.md 2020-11-13 09:04:55 +00:00
index.html removed dotnet and java version of libs 2021-03-20 13:42:22 +11:00
package.json 4.2.2 release 2020-10-28 16:11:03 +00:00

README.md

NOTE 09.11.2020 : Development on mxGraph has now stopped, this repo is effectively end of life.

Known forks:

https://github.com/jsGraph/mxgraph

https://github.com/process-analytics/mxgraph

mxGraph

mxGraph is a fully client side JavaScript diagramming library that uses SVG and HTML for rendering.

The PHP model was deprecated after release 4.0.3 and the archive can be found here.

The unmaintained npm build is here

We don't support Typescript, but there is a project to implement this, with this repo currently used as the lead repo.

The mxGraph library uses no third-party software, it requires no plugins and can be integrated in virtually any framework (it's vanilla JS).

Getting Started

In the root folder there is an index.html file that contains links to all resources. You can view the documentation online on the Github pages branch. The key resources are the JavaScript user manual, the JavaScript examples and the JavaScript API specificiation.

Support

There is a mxgraph tag on Stack Overflow. Please ensure your questions adhere to the SO guidelines, otherwise it is likely to be closed.

If you are looking for active support, your better route is one of the commercial diagramming tools, like yFiles or GoJS.

History

We created mxGraph in 2005 as a commercial project and it ran through to 2016 that way. Our USP was the support for non-SVG browsers, when that advantage expired we moved onto commercial activity around draw.io. mxGraph is pretty much feature complete, production tested in many large enterprises and stable for many years.

Over time you can expect this codebase will break features against new browser releases, it's not advised to start new projects against this codebase for that reason.