Sigma Paint

A lightweight C# / WPF paint app project with a plugin/add-on system.
This repo is mostly a “learn-by-building” playground: WPF UI, styling, and a modular architecture for extending the editor with external add-ons.

Topics: paint, C#, .NET, WPF, plugins system.

---

What’s in this repository

• WPF app (Paint.sln, Paint.csproj, App.xaml)
• A structured codebase (Classes/, Forms/, Styles/)
• Plugin folder (Plugins/) — place external add-ons here
• Add-on examples (Addons-Examples/) — reference implementations / templates
• App data/config (Program/ Data/)
• Images/resources (Images/)

---

Getting started

Requirements

• Windows
• Visual Studio (2019/2022 recommended)
• .NET workload for desktop (WPF)

Build & Run

1. Clone the repository:

   git clone https://github.com/CyberYagir/Sigma-Paint.git

2. Open Paint.sln in Visual Studio
3. Restore NuGet packages (VS usually prompts; otherwise: right click Solution → Restore NuGet Packages)
4. Build and Run (F5)

---

Plugins / Add-ons

This project is designed around the idea of “drop-in” extensions.

Using an existing plugin

1. Build (or obtain) a plugin .dll
2. Drop it into the Plugins/ folder
3. Launch Sigma Paint

Creating a plugin

Check Addons-Examples/ for the expected structure and entry points.
Typically, you create a Class Library project, reference the main app (or shared interfaces), implement the plugin interface(s), then output the DLL into Plugins/.

The exact interfaces / contracts live in the project source—start by searching for Plugin, Addon, or interface names in Classes/.

---

Repository structure (quick map)

.
├── Addons-Examples/
├── Classes/
├── Forms/
├── Images/
├── Plugins/
├── Program/ Data/
├── Properties/
├── Styles/
├── Paint.sln
└── Paint.csproj

---

License

No license file is included yet. If you want others to reuse this project (or your plugin API), add a LICENSE file and clarify third‑party package licensing.