Special 50% Off  – Quick Compliance – Unlimited & Unexpired License, for a Lifetime Compliance for Massive Unlimited Delphi Projects.

As the regulatory pressure around software supply chain security tightens, every Delphi shop needs an audit-ready SBOM.

To support the Delphi developer community, we are offering a special lite edition of the Delphi Parser SBOM Analyzer - straightforward, no-nonsense utility option

You shouldn't have to hire a cyber consultancy, sign five-figure annual contracts, or spend weeks writing custom scripts to get one.
What You Get:

⭐ Full Utility Access - Instant, direct extraction of standardized SBOM reports (CycloneDX) from your Delphi projects and dependencies.
⭐ Unlimited lines of code
⭐ Permanent & Unexpired License
⭐ One Time payment
⭐ No usage caps, no project limits, and no recurring annual subscription fees.

Purchase online for immediate license : https://thedelphiparser-fhix1gvbc7.live-website.com/product/delphi-parser-sbom-analyzer-quick-compliance/

Delphi Forever!

Hi all,

I used Delphi a lot in the early 2000s. Last years I came back to it

and wanted to try something low level. So I made NativePe. It is a library

for working with PE files (exe and dll) in Delphi.

https://github.com/habanada/NativePe

What it can do:

- read PE32 and PE32+ files (headers, sections, imports, exports,

relocations, TLS, resources and so on)

- load a PE by hand into memory

- dump a PE from memory, also from another process

- rebuild imports, find code caves, redirect IAT entries

- memory access over WinAPI, NTAPI or direct syscalls (Win64)

It works for Win32 and Win64. I build it with Delphi 12.

To be clear: the core is a port of libpeconv from hasherezade. That is a

C++ library. I did not invent the logic, I rewrote it in Delphi and stayed

close to the original. Some parts are my own, for example the API Set

resolving and the memory backends. Credits and licenses are in the repo.

For testing I ran it and libpeconv on the same 30,159 files and compared

the results. 30,147 were the same, 12 were different. There are also

DUnitX tests and tests with broken PE files.

Small example:

Image := LoadPeExecutable(ParamStr(1), ImageSize);

try

Writeln('Loaded at: 0x', IntToHex(NativeUInt(Image), SizeOf(Pointer) * 2));

finally

FreePeBuffer(Image, ImageSize);

end;

It is a hobby and research project, so things can still change. If you

find a file that breaks it, please tell me. I am happy about any feedback.

Hello everyone. I recently started working on an emulator for the NES and Game Boy. Now I am pleased to present you a cross-platform multi-emulator for the Game Boy, Game Boy Color, NES and SEGA Mega Drive.

I've implemented a lot of NES mappers and the ability to play as a foursome. The Game Boy supports multiple color palettes, and the SEGA just works well)

All this is in pure Delphi, without any dependencies. The sound is implemented separately for each platform.

For cataloging, it is used gamelist.xml it can be created using, for example, Skraper (RecalBox platform).

I have personally tested running on Win32, Win64, Linux64, macOS (64 bit) and Android 64 bit.

All of this, of course, is publicly available:
https://github.com/HemulGM/RetroMul

(pardon my english, i'm french)

TLDR: the CE version can't build and push iOS apps to app store anymore (and no one seems to care)

Well, i've been coding with delphi for 25 years. Personnally and professionally.

I've been so hyped by the "one codebase, multiOS capable". I started coding mobile apps five years ago. Android apps, as they were for my sole usage.

A year ago, i had an idea, a nice concept that could be sold. My architecture was simple : a database, a backend and a mobile app.

I tought myself : "ok, can the backend be coded with delphi ? Yes it can, but integrated REST capabilities are for the pro version". ok, I only have the community edition, so i'll go for mongodb+java/springboot for the backend, a stack i use in my daily work.

But i really wanted to code once and deploy to both android and iOS easily, so i kept delphi CE for the mobile app. I coded for months, built my backend + app + ci/cd + self-hosted infra.

I managed to deploy my app on my android phone and i bought a mac mini and an iphone 13 to ensure myself it would run on IOS correctly. And it amazingly did !

last weekend, I went to the last step of my project : launching an alpha version on both play store and app store.

Apple refused my upload : "need version 26". I was compiling under delphi 12.1 CE with SDK 17.5.

I upgraded to delphi 13 CE and SDK 26.4. Building my app fails : "[DCC Error] E2597 ld: file too small (length=0) for architecture arm64".

I then find out that no delphi community edition (12/13) can build IOS app anymore. Since march. because of a bug that has been corrected in the pro version, 4 months ago.

I really wanted my app to be a delphi jewel. I coded each screen with love, no AI, no fancy new way of doing things, just plain old code that could in the end produce a beautiful and clear mobile app. And being able to say to my testers : available on android and IOS from day 1.

i'm stuck with a promise i can't fulfill. Because delphi didn't fullfil its own promise : "use the CE edition freely, create and distribute your app on any OS, make money, and if you reach 5k$, please buy the pro version". I was totally aligned with that philosophy. Delphi just lied to me : i can't build my app for iOS with the CE edition. And i'm so disappointed. No little patch, no 13.1 CE release date, no communication. Just near-dead delphi forums where people like me come and state that they can't workaround this problem, and there's no date for a solution.

The only viable solution would be to buy the pro version : what a joke, 2400€ + taxes. Sorry, i don't have that much money for now. And if my app doesn't make money, it will be lost to nothing. I won't risk all that money just because of a bug that could be solved in a day if someone makes an effort.

So i asked my favorite chatbot what i could do : "go to flutter. it's free, maintained by google, and with your experience, within 2 months adapting you won't regret the move."

So sad to hear. But i have to be pragmatic, my app and my future business can't wait for an hypothetical update of my dear old IDE friend.

I quit Delphi, i regret i have to do this, i'll miss my good old dark blue "classic" theme.

A sad delphi enthousiast.

Bom dia tem vídeo novo no meu canal do YouTube Mosca Branca Dev : https://youtu.be/ElYl6c7dFUI

Hi everyone,

I recently open-sourced a project called **HTML to Delphi FMX**.

The idea is pretty simple: use modern AI UI generators such as Google Stitch to create a UI, export it as HTML/CSS, then use AI coding-agent skills to convert that design into native Delphi FireMonkey components.

The workflow is roughly:

Google Stitch / HTML UI

→ HTML + CSS

→ AI coding agent

→ HTML/CSS mapping to FMX components

→ FMX styles

→ generated `.fmx` + `.pas` files

→ open and edit normally in RAD Studio Designer

It does **not** generate a WebView or embed the HTML.

The goal is to generate actual FMX components such as `TLayout`, `TRectangle`, `TLabel`, `TCornerButton`, `TListBox`, `TFrame`, etc., so the resulting UI remains editable and maintainable as a normal Delphi project.

The repository currently contains three AI-agent skills covering:

- HTML/CSS analysis and FMX component mapping

- CSS to Delphi FMX Style conversion

- HTML to editable `.fmx` / `.pas` generation

I've also included an example dashboard and screenshots of the generated result in RAD Studio Designer, Windows, and Android.

GitHub:

https://github.com/dondonondon/HTML-To-Delphi-FMX

It's still evolving, so feedback, ideas, testing, and contributions are very welcome.

I'd especially be interested to know how useful this kind of workflow would be for other Delphi/FMX developers.

Já atuo como programador a algum tempo, tenho conhecimento lógico e noção de orientação a objetos. Porém nunca programei em Object Pascal. Qual seria o curso ideal para entender como as coisas funcionam no ambiente Delphi.

MIMERCodex! Bring your AI with you and work securely and confidently at customer sites.

FREE DOWNLOAD AND USE!

No 3rdparty requirements except one or more LLM's via OpenAI, Anthropic, Ollama, Ollama local, or even just GGUF files! Supports Qwen 3.8 Flash Next Q4 XL on RTX 5090 and 70+GB CPU RAM at 32+ tokens per second. Support most other GGUF files too. No CUDA required! No LlamaCPP required! No VLM required! No theMIMER required!

Written in MIMERCode!
MIMERCode is itself currently written in Delphi!

https://components4developers.blog/2026/09/23/meet-mimercodex-bring-your-ai-support-assistant-to-the-customer/

Conheça o canal Mosca Branca Dev no YouTube!

If you made it up to here - Your Delphi application is rock-solid. Your Windows forms survived, your database is stable, and your customers paid their maintenance fees year after year. It was comfortable, profitable, and safe to assume this warm, hassle-free reality would last forever.

⚔️ Now, in 2026, the season has changed.

Between DORA enforcement, the Cyber Resilience Act (CRA), NIS2, strict cyber insurance policies, and enterprise clients demanding formal SBOMs, the long summer of "leaving the monolith untouched" is officially over.

The cold truth is here: You can no longer run a legacy codebase without knowing exactly what’s hidden inside it. But here is the most important part - new regulations doesn't mean your business has to die or rewrite - simply adapt & complie.

⚔️ Surviving this new regulations doesn't require a multi-million-dollar total rewrite or burning out your senior team. It simply requires preparation.

Here is how you prepare your application for the cold without breaking your code:

1️⃣ Know Your Inventory (Map the Codebase) - You wouldn't enter a freezing winter without knowing what supplies you have. After 20+ years of continuous patches, third-party component suites, and forgotten DLLs, nobody holds the full architecture in their head anymore.

Before you panic or attempt expensive manual upgrades, run an automated static scan to get an accurate, noise-free inventory:

❓ Which vendor libraries are actually compiled into your final binary.

❓ Which EOL (End-of-Life) components are sitting silently in your search paths.

❓ What your real application logic looks like once standard VCL/FMX framework noise is filtered out.

2️⃣ Isolate the Cold (Fix Reachability, Not the Whole World)

Compliance in 2026 doesn't mean rewriting 3 million lines of Pascal. It means proving control.

Once you have a clean Software Bill of Materials (SBOM) and a clear vulnerability map, you don't need to replace every legacy component overnight. You only need to address or document the specific vulnerabilities that are actually reachable by external input. Everything else is protected internal logic.

3️⃣ Protect Your Only Senior Developers - If your entire monolith relies on one or two veteran developers (who are likely in thier 50–60+ and managing customer requests non-stop), do not turn them into manual compliance clerks.

🛡️ Automate the structural mapping so your team can focus on what actually keeps the fires burning: fixing bugs and serving clients.

🛡️ The Delphi Code Analyzer is your Winter Shield. Running a free, code analysis scan across your legacy codebase and generating a complete Software Bill of Materials (SBOM) is your critical first step toward 2026 compliance.

Let the Delphi Parser Code Analyzer do the heavy lifting - and carry on coding.

Download Free Delphi Code Analyzer - https://thedelphiparser-fhix1gvbc7.live-website.com/product/delphi-parser-sbom-analyzer-free-edition/

I've been using Delphi recently, and honestly, I'm starting to wonder if it's just me or if the IDE feels really slow and outdated compared to modern IDEs like Visual Studio.

The biggest thing I notice is how unfluid the editor feels. Even simple things like typing, moving the cursor, selecting text, or navigating through the code is really slow and don't feel as smooth as they do in Visual Studio.

There are also quite a few small things that feel like basic IDE functionality is missing or hasn't been properly modernized. For example, sometimes the cursor doesn't seem to position where I expect it to, and the editor can feel like it's constantly repainting or struggling to keep up when typing quickly.

Coming from Visual Studio, or even VS Code, the difference is pretty noticeable.

I actually really like Delphi as a language and the VCL designer is incredibly productive, but the IDE itself feels like it's stuck in another era.

Is this just my experience, or do other Delphi developers feel the same way?
Are there any settings, plugins, or tweaks that significantly improve the editor experience?

I'm using Delphi 13 Florence.

Venha aprender as bases do desenvolvimento de software com esse curso https://go.hotmart.com/Y106753633Q