A Decade of Magnum
On 19th December 2010, Magnum saw its first commit. A bunch more commits happened since then and I learned some things along the way.
On 19th December 2010, Magnum saw its first commit. A bunch more commits happened since then and I learned some things along the way.
During the past four months, Magnum began its adventure into the Python world. Not just with some autogenerated bindings and not just with some autogenerated Sphinx docs — that simply wouldn’t be Magnum enough. Brace yourselves, this article will show you everything.
Magnum is developed with a “Zen Garden” philosophy in mind, focusing on productivity, predictability and ease of use. Let’s see how that can extend beyond just the library itself — into your daily workflow.
Whether you are browsing Magnum docs or use Doxygen for your own C++ documentation, there’s always a way to improve your workflow. This article presents the most recent additions to the m.css Doxygen theme.
Magnum docs were missing the search functionality for some time because I wanted to implement it properly for the new theme. The proper implementation is now ready.
One of the goals while building the new Magnum website was to lower the barrier for contributing content. With Git and GitHub it’s already very easy to contribute code to the project itself, so why not extend that to the website as well?
The new website does a better job at clearly presenting engine features and enables the team to share progress easier than before. Besides that, its development resulted in many valuable byproducts for both C++ developers and web content publishers.