<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on RapidEE</title><link>https://rapidee.com/en/blog/</link><description>Recent content in Blog on RapidEE</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rapidee.com/en/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>What really changed in RapidEE 10.0</title><link>https://rapidee.com/en/blog/rapidee-10-what-changed/</link><pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate><guid>https://rapidee.com/en/blog/rapidee-10-what-changed/</guid><description>In the previous post I explained why RapidEE had to be rewritten. Now for what actually changed.
A new look You see the new interface as soon as the program starts: the variable trees are still where they were, but everything around them has been brought up to date.
Instead of the old collection of skins, there are now two themes: dark and light. I hope you won&amp;rsquo;t miss the old ones too much.</description></item><item><title>Why RapidEE 10.0 was rewritten</title><link>https://rapidee.com/en/blog/rapidee-10-rewritten-in-csharp/</link><pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate><guid>https://rapidee.com/en/blog/rapidee-10-rewritten-in-csharp/</guid><description>RapidEE began in 2007 and was written in Delphi for almost its entire history — that code survived several generations of Windows.
Over the years the project went through five generations of Delphi — 7, 2007, 2010, XE2 and, finally, 10.2 Tokyo. Each move meant a substantial update of the project and another round of compatibility checks for third-party components.
And there were quite a few: Virtual Treeview for the main tree, Toolbar2000 and SpTBXLib for the interface, GNU gettext/dxgettext for localization, madExcept for crash reports, FastMM4 for memory diagnostics, DSiWin32 and PNGImage for system functions and images.</description></item><item><title>Why Tolgee for translations</title><link>https://rapidee.com/en/blog/why-tolgee-for-translations/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://rapidee.com/en/blog/why-tolgee-for-translations/</guid><description>While rewriting RapidEE 10.0, I wanted to keep ordinary .resx files in the application while letting translators work with them in a browser. I needed a simple workflow: source strings go up from the project, translations are edited online, and then exported back into the resources.
For scale: RapidEE&amp;rsquo;s English resource currently has about 120 keys, and the interface is translated into more than 30 languages. When comparing services, a key and a translation are not the same thing: one key in 30 languages is still one key, even though it has 30 translations.</description></item></channel></rss>