<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Egui on Rusty Electrons</title><link>https://www.rustyelectrons.com/tags/egui/</link><description>Recent content in Egui on Rusty Electrons</description><generator>Hugo -- 0.152.1</generator><language>en-za</language><lastBuildDate>Sun, 01 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.rustyelectrons.com/tags/egui/index.xml" rel="self" type="application/rss+xml"/><item><title>Integrating VTK into egui (for EM simulations)</title><link>https://www.rustyelectrons.com/posts/7-integrating-vtk-into-egui/</link><pubDate>Sun, 01 Jun 2025 00:00:00 +0000</pubDate><guid>https://www.rustyelectrons.com/posts/7-integrating-vtk-into-egui/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;I am currently working on an EM simulator for which I will need 3D visualisation capabilities. As usual I have decided to &amp;ldquo;overcomplicate&amp;rdquo; matters by using a very &amp;ldquo;unique&amp;rdquo; assortment of programming languages and libraries to do this (both for fun and to learn new things). Naturally, I want to use Rust for this project. This is not only because simulation software needs to extract as much performance from the hardware as possible, but also because I really appreciate Rust&amp;rsquo;s rich and rigid type system when building large projects as it helps keep things organised. And then there is the rich library ecosystem associated with Rust which usually comes in very handy but turns out to be somewhat limited in this particular case (at the time of writing). If easy library access were my primary factor under consideration, Python would likely be the best choice for this project.&lt;/p&gt;</description></item></channel></rss>