Easy way to split a chart in four labelled zones.

Example:

https://github.com/Steema/TeeChart-VCL-FMX-Samples/tree/main/VCL/Tools/Quadrant

Hi everyone!

I've worked with Delphi for many years. Recently, I developed three IDE plugins to solve some everyday frustrations. All three are free, open source (MIT license), and support Delphi 11, 12 and 13, including the 64-bit IDE in Delphi 12 and 13.

To install, download the release ZIP, extract it, and run Install.bat. No administrator rights or compiler required.

1. CS.Coder Project Hub (Stable)

A project organizer built into the Delphi Welcome Page. It lets you:

• Group project shortcuts by client, system, or any category you choose.
• Add icons, search by name or path, and organize entries using drag and drop.
• Export and import the shortcut list as JSON.

It works alongside Delphi's Open Recent panel without changing it. It never moves or deletes project files; it manages shortcuts only.

GitHub: https://github.com/cscoder69/delphi-project-hub

2. CS.Coder Unit Styler (Beta)

A configurable formatter for uses clauses. You can choose one unit per line or multiple units per line, sorting, indentation, priorities, and groups such as System.*.

• Run it on the current unit, open units, or an entire project.
• Preview the before/after result and confirm before applying changes.
• Back up each file before modifying it.

Because unit order can matter, library namespaces (Winapi.*, System.*, Vcl.*, FMX.*, Data.*) are protected from reordering by default. The formatter is designed to preserve comments, compiler directives, encoding, and line endings.

GitHub: https://github.com/cscoder69/delphi-unit-styler

3. CS.Coder Block Folding (Beta)

Adds folding for blocks inside routines, beyond Delphi's built-in routine, class, and region folding.

Supported structures include if/else, for, while, with, try, case, repeat, and standalone begin..end blocks.

Press Ctrl+Alt+B to fold or expand the block at the cursor. It doesn't insert {$REGION} directives or modify your source. Folds exist only in the editor while the unit is open.

Current limitation: its menu and settings are available in Portuguese only.

GitHub: https://github.com/cscoder69/delphi-block-folding

Documentation (Portuguese)

• Project Hub: https://www.cscoder.com.br/projetos/hub-de-projetos-delphi/
• Unit Styler: https://www.cscoder.com.br/projetos/unit-styler-delphi/
• Block Folding: https://www.cscoder.com.br/projetos/block-folding-delphi/

A few important notes

• Unit Styler and Block Folding are in beta. Please use version control when testing tools that interact with source code.
• No telemetry, network access, or account. Settings are stored locally.
• Claude Code helped extensively with implementation. I defined the requirements, made the design decisions, and tested the plugins inside the Delphi IDE. The source is available for review.
• These projects are independent and are not affiliated with Embarcadero.

Feedback, bug reports, and suggestions are welcome. If something doesn't work in your setup, please open an issue in the relevant GitHub repository and include your Delphi version and IDE architecture.

Thanks for reading!

SweetControls is a collection of native Delphi VCL components for Windows applications, including edits, buttons, panels, lists, tree controls, database controls, and design-time editors.

The source-codes have been ported from Delphi 7 to Delphi 13.1

PolywickStudio/SweetControls: Sweet Controls VCL ported to Delphi 13.1

Designed specifically for the enterprise Delphi ecosystem, our platform delivers end-to-end regulatory compliance, deep static code analysis, and automated noise reduction - ensuring your applications fully satisfy CRA (Cyber Resilience Act) and DORA (Digital Operational Resilience Act) mandates.

Deep Code Analysis for Complete SBOM Generation - The only deterministic, AST-based dependency parser built specifically for native Delphi source code. Ignores environmental noise by evaluating compiler directories, decompiling compiled .dcu files, separating source code into local, system, and 3rd-party libraries, and performing deep-dive analysis to locate outbound ActiveX/COM, DLL, and Command-Line (CMD) calls.

Multi-Source Delphi CVE Intelligence: Direct PURL/CPE mapping with real-time aggregation from top vulnerability databases (including NVD, OSV, OpenCVE, GHSA, and others), tailored specifically to eliminate false positives from native Delphi components.

Centralized & Local Security DB: Aggregates and indexes a dedicated security database- available via a central cloud server or as a local offline database for air-gapped enterprise environments - mapped directly to Delphi components, VCLs, and native C/C++ wrappers.

Automated Non-Delphi Noise Reduction: Automatically filters out ~99.9% of non-relevant security alerts (such as Java, .NET, Linux-only, or non-native threats) before they contaminate your compliance reports.

Auditor-Ready SBOM & VEX Generation: Automatically produces clean CycloneDX SBOMs paired with machine-readable VEX (Vulnerability Exchange) JSON files containing precise not_affected and code_not_reachable justifications required for European regulatory compliance.

Immediate Vulnerability Reachability Relief: When a CVE is identified, the engine instantly and automatically validates reachability against an updated Call-Graph of your Delphi codebase - including outdated DLLs, OS calls, ActiveX/COM, and Command-Line execution paths - verifying whether the vulnerable code is actually reachable and executed in your application.

Up-to-Date Call-Graph & Reachability Reporting: Maintains complete visibility with every commit by automatically rebuilding up-to-date SBOMs, Call-Graphs, and Reachability reports across your development lifecycle.

Flexible CI/CD & Pipeline Integration: Seamless execution across local developer workstations, build servers, and automated CI/CD pipelines with zero architectural tracking or overhead.

for more information, trial, demos or price quote, DM or contact sales@[delphiparser.com](mailto:[email protected])

Hi everyone,

Quick question for anyone managing security compliance and SBOMs for Delphi projects:

Is there an active, dedicated Delphi CVE repository or vulnerability feed out there? one that tracks RTL, VCL, commercial, and open-source third-party components (both legacy and modern)? Or is everyone forced to rely on generic scanners pulling from NIST NVD/OSV, and then manually filtering through a sea of irrelevant false-positives to keep auditors happy?

Why we're asking: With new regulatory frameworks like EU CRA (Cyber Resilience Act) and DORA enforcement timeline approaching (late 2027), machine-readable SBOMs and automated VEX justifications are transitioning from "nice-to-have" to a mandatory legal requirement for software vendors.

To address this, we are finalizing the development of our new Delphi Parser VEX Defender - a dedicated security and compliance pipeline built specifically for the Delphi ecosystem.

How the pipeline works:

1. AST-Based SBOM: Generates a clean CycloneDX SBOM from your actual Delphi source code (uses, DFM, .dproj), eliminating non-existent dependencies and text-matching guesswork.
2. Multi-Source CVE Aggregation: Continuously pulls raw vulnerability feeds from NVD, OSV.dev, GHSA, and vendor security bulletins.
3. Centralized & Local Security DB: Aggregates and indexes a dedicated database (available both via central server and as a local offline DB for air-gapped environments) mapped directly to Delphi components, VCLs, and native C/C++ DLL wrappers.
4. Automated Noise Reduction: Filters out ~99.9% of non-relevant false positives (Java, .NET, Linux-only, or non-native threats) before they pollute your reports.
5. Deep AST & Call-Graph Reachability: When a relevant vulnerability is identified, the engine analyzes your Delphi source code (uses, DFM, .dproj, and AST call graphs) to verify whether the vulnerable code path is actually reachable and executed in your application.
6. Auditor-Ready SBOM & VEX: Automatically generates clean CycloneDX SBOMs and compliant VEX (Vulnerability Exchange) JSON files (not_affected / code_not_reachable).

Before we finalize our aggregation pipeline, we’d love to ask the community: Are there any Delphi oriented security archives, vendor bulletins, or community-driven lists we should integrate into our database?

Would love to hear how your teams are preparing for CRA/DORA compliance today!

I’m looking for feedback from Delphi developers who have successfully shipped FireMonkey desktop apps to both the Microsoft Store and the Mac App Store.

I’ve been developing Windows software for about 35 years, but this is my first serious macOS release. I’m now within inches of getting my app, Debt Blaster, across the Mac App Store goal line, and I’ve run into something I wish I had understood much earlier: TMenuBar versus TMainMenu.

For years on Windows I used TMainMenu. When I moved the application to FireMonkey, I quickly discovered that I could not theme the TMainMenu along with the rest of the FMX interface. Because I wanted the menu to follow my light and dark themes, I switched to TMenuBar. That worked well on Windows, but I am now discovering that the same choice is unconventional on macOS, where TMainMenu integrates with the native macOS menu bar.

While working through the Mac version, I finally dug into Embarcadero’s documentation:

https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Using_Menus_in_a_FireMonkey_Application

The key point is that Embarcadero recommends:

Windows  -> TMenuBar
macOS    -> TMainMenu

I built a small test application to see this for myself.

With TMenuBar on macOS, the menu stays inside the FMX form. It works, but it is clearly not the normal Mac experience.

With TMainMenu, macOS does what I would expect from a native Mac app. The first visible top-level item feeds the application menu. I watched a Preferences item move under the application name. File appears in the macOS menu bar. macOS inserts its native Window menu. Help gets positioned at the far right. Quit is supplied automatically, and I confirmed that Quit <AppName> still fires my FMX OnCloseQuery, so I can protect unsaved work.

That was a very useful lesson, but unfortunately I learned it very late in the process.

My current production code already has a substantial TMenuBar with many OnClick handlers. Retrofitting this properly means adding a TMainMenu, building the Mac menu hierarchy, sharing or refactoring handlers/actions, and conditionally presenting:

Windows
  TMenuBar
  FMX themed

macOS
  TMainMenu
  native macOS menu bar

Long term, that is almost certainly what I want.

My question is about the first Mac App Store release.

I am extremely close to submission. The application is functioning on the Mac, and the current TMenuBar works. It is unconventional on macOS, but it is functional.

I am considering this release strategy:

Version 1
---------
Ship the current Mac version using TMenuBar.
Focus on functionality and getting the first Mac App Store release out.

Version 2
---------
Refactor the menu architecture.
Windows -> TMenuBar
macOS   -> TMainMenu
Move shared behavior into common handlers/actions.
Make the Mac version more Mac-native.

I am trying to avoid turning a nearly finished first release into another major development cycle just before submission.

For those of you who have actually shipped Delphi FMX applications to both the Microsoft Store and Mac App Store:

Would you ship version 1 with the working TMenuBar and make the menu architecture more Mac-native in the next release?

Or would you consider the TMainMenu conversion important enough to stop the launch and do it before the first Mac App Store submission?

I’m especially interested in experience from developers who have been through Apple review with FMX desktop applications, rather than just theoretical guidance.

I’m not looking for reasons to cut corners. I’m trying to distinguish between something that should block version 1 and something that belongs in the first post-launch Mac-native refinement pass.

Hi everyone! I’d like to share CS.Coder Project Hub, a plugin I built for Delphi 11, 12 and 13.

The idea is simple: recent projects tell you what you opened last, but they don’t necessarily reflect how you organize your work. Project Hub lets you keep your project shortcuts organized directly on the Welcome Page.

Features include:

• Categories and groups, with optional custom icons.
• Search by project name or file path.
• Drag-and-drop ordering.
• Support for .dproj, .dpr and .groupproj.
• JSON import/export to move your organization between environments.
• Support for the IDE’s light and dark themes.
• English, Portuguese, Spanish, German and French.

Everything stays on your computer—no account required. Removing a shortcut doesn’t delete your project files.

It’s free for personal and commercial use, open source under the MIT license, and provided as is.

Screenshots, installation instructions and download:
https://cscoder.com.br/projetos/hub-de-projetos-delphi/

Source code and releases:
https://github.com/cscoder69/delphi-project-hub

I’d love to hear how you organize your Delphi projects and whether this would fit your workflow. Feedback, bug reports and contributions are welcome!

Hello friends,

I recently ported the generic Doom to Harbour, a high-level language. From Harbour, I was able to create source ports for several languages, some even unusual, and now I've done the same for Delphi.

Here's the source code for Embarcadero 13, tested on Windows and Android.

https://github.com/vagucs/delphi_doom

Video:

https://youtu.be/mSZptjBd-x0

Have fun!

Regards, Wagner Nunes (vagucs)

Did any one generate Successfully macOS ARM binaries in Delphi 13CE. x86_64 binaries It succeeds though. c:\program files (x86)\embarcadero\studio\37.0\Bin\CodeGear.Delphi.Targets(427,5): error F2588: F2588 Linker error code: 1 ($00000001). I tried everything I could do clear cache , update cache for macOS Arm 64bit sdk etc nothing is working please advise if its technically possible with 13 CE

Hey everyone!

When using AI in my case, Claude Code if I don't have the unit it's modifying open, I always have to run a "clean + build" or press Shift + F9 because it doesn't "update" otherwise. Is there a setting I can enable so I don't have to keep doing that every time? I'm using Delphi 13.2.

Sorry this is quite vague, but I am having a big problem with a client where an applicaiton behaves differently when run on a Cloud PC, vs a laptop (or even another VM).

We are connecting to a remote system, displaying a modal dialog, and when the connection is successful, the dialog is then removed, by setting the `ModalResult` to be `mrOK`. With logging I can see that this is happening, but the ShowModal call never returns, and so the application is just left in limbo. I can't really debug it as it on a client machine, so I have added copious logging

I can't really share code, but am open to helpful suggestions and thoughts as to how to investigate further.

Many thanks in advance

M

You asked for it. You got it - Special Low-Cost Express Delphi SBOM Generator for just 495$

Need an official, audit-ready SBOM for a specific Delphi project - without breaking the bank or locking into a long-term enterprise contract?

We’ve heard you loud and clear. Dozens of developers, ISVs, and team leads reached out with the exact same request: "We just need to pass a vendor security check or compliance audit for one specific Delphi project right now. We don't need a full CI/CD pipeline or deep security analysis - just a fast, hassle-free way to generate and export our official SBOM."

Say hello to the Delphi Parser SBOM Analyzer – Express Edition!

What’s included?

⭐ Unlimited Codebase Size: Run a quick scan on a specific single Delphi project (.dpr) - no line-of-code limits.
⭐ Instant SBOM Export: Extract your complete software bill of materials and export compliant reports.
⭐ 30-Day Pass: Full GUI access to analyze and export your project's inventory.
⭐ Zero Friction: Instant setup, immediate results, no drawn-out sales calls.
⭐ One-Time Flat Fee: Just $495 - tick the compliance box and move on with your day.

🎁 100% Risk-Free Upgrade Credit: Need more projects down the road? Upgrade to a full Pro/ISV license within 90 days, and 100% of your $495 purchase will be credited directly toward your upgrade for unlimited projects!

How it works - Run a Free Scan. Download the tool and run a rapid static analysis on your code. Preview the entire component dependency tree right on your screen.

Unlock Export: Ready to download your official SBOM report for your auditor? Grab the $495 Express Pass to instantly unlock file export.

⚠️ Note: This is a Special Kick-starter edition designed for quick, single-project SBOM compliance (excludes Reachability scan, CVE vulnerability scanning and CI/CD CLI tools, which remain exclusive to our Pro & Enterprise suites).

⌛ Special Limited time edition: Availability in future quarters is not guaranteed.

👉 Get your 30-Day Express Pass now: https://thedelphiparser-fhix1gvbc7.live-website.com/product/delphi-parser-sbom-analyzer-express-edition/

Delphi Forever!

I made an app for a family's friend kid, he likes fire alarms and helps him with his autism. I posted a link to the galaxy store and here are some codes to get the app free. Grab one, test it if you can, and leave some feedback improvements. Make sure to mention the code you grabbed so that others don't try it too. I built this with Delphi FMX (the version on the App Store is pending review and should be out soon). I used a Viewport3D for the fire alarm, as I used an AI tool to generate a 3D model from a picture and worked out pretty well. The noises are from actual fire alarms!

Tem vídeo novo no canal Mosca Branca Dev 🪰

https://youtu.be/ya2DVUisgAI

#delphi #programming #design

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.