By Arjan Molenaar on July 31, 2020
Gaphor as a project has been around for almost 19 years. I checked the source code repository and I made the first commit on December 21, 2001.
The project started after I had an intership where I had to work with Rational Rose. This product was (and is, I suppose) very complex and has a high learning curve. I thought I could do better. With that attitude I started writing my own UML modeling tool.
One of the first choices to make for a GUI application is the toolkit to use. GTK+ seemed like a solid option: it’s 100% open source (contrary to QT, for example), and was used in big projects, such as GIMP and (GNOME)[https://gnome.org]. Looking back, I’m still happy with that decision.
The main component of a diagramming tool is the canvas. I worked on Linux at the time and the most complete diagramming application at the time was Dia. I could not reuse their canvas component, though, since it was interwoven with the rest of the application. The initial canvas component for Gaphor I called Diacanvas. It mimics the behavior of Dia (and Visio) and was used to build the first couple of versions of Gaphor.
The Diacanvas library was written in C. Gaphor was written in Python from the start. At some point this started to cause friction. In 2006 the canvas library was rewritten in Python and Gaphas was born. At this time Artur and me were th emain contributors.
The project moved on, but lost traction after the 0.17.1 release in September 2011.
In early 2017 Dan Yeaw contacted me. He wanted to work in Gaphor and add SysML support. At this time, I was no longer working on Gaphor at all, so Dan became the maintainer. The main repository moved to the Gaphor organization at GitHub and Dan made a huge effort to bring the code up to date. The source code was hardly updated since 2011. A time where Python 2 was the norm and GTK+ 2 was the GUI toolkit (PyGTK). By now, Python 3 was the norm and GTK+ 3 had been available for years.
At some point — it’s late 2018 — Dan got stuck and we had a video call to discuss the issues he ran into migrating and updating Gaphor. I agreed to help out a bit to get him going. I guess the help never stopped. Working on Gaphor again made me realize how much fun it is to work on such a project.
It took us more than a year to get the code and internals up to date, to a level we felt confident we can add another modeling language. Gaphor 2.0 is the result. A fully updated modeling environment for casual users and die-hard modelers. The application is rapitly improving and the user base is growing.
Give Gaphor a try and let us know what you think!