ABACOM - ELECTRONIC SOFTWARE

I've developed a Sprint Layout Plugin Manager that allows you to manage and run multiple plugins from one convenient interface.
No more redefining plugins each time you want to use a different one — simply select the plugin you want from the list and run it directly.

Main Features
Centralized plugin list – Manage all your Sprint Layout plugins from a single location.
Friendly names – Assign easy-to-remember names to your plugins.
Edit paths & rename – Quickly update plugin paths or rename them without touching the configuration files.
One-click run – Double-click or press Enter to instantly launch the selected plugin.
Automatic forwarding – Correctly forwards the plugin’s result back to Sprint Layout (supports exit codes 1–4 & 128–255).
🪄 About screen – With a fun touch: “One plugin to rule them all!”

How It Works
Place the Plugin Manager executable in your Sprint Layout folder.
Add your plugins once through the UI.
Select a plugin from the list and click Run (or double-click it).
If the plugin produces output for Sprint Layout, it will automatically close the manager and return the result to Sprint Layout.

Screenshot



Download & Feedback
https://github.com/cd32freak/SprintLayoutPluginManager

I’d love to hear your feedback and suggestions for improvement. If you find it useful, let me know what features you'd like to see next!

Thanks a lot. It's a nice plugin.

But there aren't many plugins.

If the Abacom team had a detailed explanation about the plugin development, it would guide the developers.

Yes, it's true, that's the reason why I created a C# plugin demo to show users how to get started developing their own plugin:
viewtopic.php?f=70&t=6058

burhan hat geschrieben: Freitag 3. Oktober 2025, 21:11 Thanks a lot. It's a nice plugin.

But there aren't many plugins.

If the Abacom team had a detailed explanation about the plugin development, it would guide the developers.

Abacom actually provides full documentation for the API data structures—check out the 'Text-IO interface' section in the manual. That’s exactly what I referenced to build sprintFont.

Writing a plugin is honestly pretty straightforward. You don't need to deal with any complex IPC mechanisms. Your plugin is just a standalone executable. Sprint-Layout passes data to it via command-line arguments, and your plugin just needs to parse a temporary file (in Text-IO format) that Sprint-Layout generates.

Once your code processes the data, it generates a new temporary file (original_filename_out.txt) and returns a specific exit code. Sprint-Layout then reads that output and applies the changes to your active PCB file. It's really that simple—nothing complicated about it. Plus, you can write the plugin in whatever language you prefer.