|
no
experience
|
0
products
|
0
demo versions
|
|
0
jobs
|
0
signals
|
0
subscribers
|
I’m a Software Architect and Developer focused on financial markets, algorithmic trading, and data‑driven systems. I work at the intersection of software engineering, quant trading, and machine learning, building everything from data infrastructure to automated strategies and tools for professional trading workflows.
I have deep expertise in MQL and the MetaTrader ecosystem, developing EAs, indicators, libraries, and tooling to make MQL development more robust, testable, and scalable.
While building products for MetaTrader, I identified a clear gap in how real‑world MQL projects manage code reuse and dependencies. To address that, I created KnitPkg (https://knitpkg.dev/), a modern Git‑first package and project manager for MetaTrader 4 and 5 that brings an npm‑like workflow, semantic versioning, and reproducible installs to the MQL community.
I have deep expertise in MQL and the MetaTrader ecosystem, developing EAs, indicators, libraries, and tooling to make MQL development more robust, testable, and scalable.
While building products for MetaTrader, I identified a clear gap in how real‑world MQL projects manage code reuse and dependencies. To address that, I created KnitPkg (https://knitpkg.dev/), a modern Git‑first package and project manager for MetaTrader 4 and 5 that brings an npm‑like workflow, semantic versioning, and reproducible installs to the MQL community.
Douglas Nascimento Rechia
** CALLING MQL DEVELOPERS: LET'S BUILD A SHARED PACKAGE ECOSYSTEM FOR METATRADER **
If you’re an MQL developer with code that could be useful to others, I’d like to invite you to help grow a new open ecosystem around reusable packages for MetaTrader 4 and 5.
I’m talking about things like:
- JSON read/write libraries
- Risk management and position sizing helpers
- GUI / chart component libraries
- Pattern recognition utilities (candlestick, indicators, etc.)
- Price action / SMC / orderflow tooling
- Any other reusable MQL library you’ve built for your own work
I’ve been working on KnitPkg (https://knitpkg.dev), a modern, Git‑first package and project manager for MQL4/MQL5 that brings an npm-like workflow to MetaTrader: semantic versioning, reproducible installs, and a registry of packages backed by Git repositories.
Now that KnitPkg is launching, I’d like to help other developers publish their own libraries into this ecosystem.
*HOW TO SHARE YOUR MQL CODE VIA KNITPKG*
If you have an MQL library you’re willing to share, the basic idea is:
1. Create a Git repository with your code on any supported host: MQL5Forge, GitHub, GitLab, Bitbucket
2. Follow the “Creating Packages” guide in the KnitPkg docs to see the structure and concepts:
https://docs.knitpkg.dev/user-guide/creating-packages/
You don’t need to get everything perfect on the first try. To make this easier during the launch phase of KnitPkg, I’m offering hands-on help.
*MY OFFER: I'LL ADAPT YOUR REPO TO THE KNITPKG STRUCTURE*
To encourage more high‑quality packages in the registry, here’s how I can help you, step by step:
1. You create the Git repo on any supported host (MQL5Forge, GitHub, GitLab, or Bitbucket) and push your existing MQL code there.
2. You send me a private message on MQL5 with the repository URL and a short note that you’d like it adapted for KnitPkg.
3. I will fork your repository, adjust the structure and manifest to match the recommended KnitPkg project layout, and open a Pull Request with the changes.
4. You review and merge the Pull Request into your repository.
5. With the structure in place, you publish your project to the KnitPkg registry by running this single command on your machine: 'kp register'. After that, your package becomes installable by any developer using KnitPkg, via a simple:
$ kp add @yourorg/yourpackage
$ kp install
*DISCOVERABILITY: YOUR CODE IN THE KNITPKG WEB REGISTRY*
Once your repository is published in the KnitPkg registry, your package will be easily searchable through the web interface:
For MQL5 projects: https://registry.knitpkg.dev/mql5
For MQL4 projects: https://registry.knitpkg.dev/mql4
Other developers will be able to discover your work by organization, package name, author, license, or project type, and install it directly into their own MetaTrader projects.
*WHY THIS MATTERS*
MetaTrader projects often grow through copy/paste and ad‑hoc folder sharing. By turning your libraries into versioned packages:
- Other traders and developers can reuse your work reliably.
- You gain a clear distribution and update channel for your code.
- The MQL community moves toward modern, reproducible workflows, similar to what JavaScript, Python, and others already enjoy.
If you’re interested, just send me a private message with your repo link and I’ll help you bring your library into the KnitPkg ecosystem.
Let’s make MQL development more modular, shareable, and professional—together.
If you’re an MQL developer with code that could be useful to others, I’d like to invite you to help grow a new open ecosystem around reusable packages for MetaTrader 4 and 5.
I’m talking about things like:
- JSON read/write libraries
- Risk management and position sizing helpers
- GUI / chart component libraries
- Pattern recognition utilities (candlestick, indicators, etc.)
- Price action / SMC / orderflow tooling
- Any other reusable MQL library you’ve built for your own work
I’ve been working on KnitPkg (https://knitpkg.dev), a modern, Git‑first package and project manager for MQL4/MQL5 that brings an npm-like workflow to MetaTrader: semantic versioning, reproducible installs, and a registry of packages backed by Git repositories.
Now that KnitPkg is launching, I’d like to help other developers publish their own libraries into this ecosystem.
*HOW TO SHARE YOUR MQL CODE VIA KNITPKG*
If you have an MQL library you’re willing to share, the basic idea is:
1. Create a Git repository with your code on any supported host: MQL5Forge, GitHub, GitLab, Bitbucket
2. Follow the “Creating Packages” guide in the KnitPkg docs to see the structure and concepts:
https://docs.knitpkg.dev/user-guide/creating-packages/
You don’t need to get everything perfect on the first try. To make this easier during the launch phase of KnitPkg, I’m offering hands-on help.
*MY OFFER: I'LL ADAPT YOUR REPO TO THE KNITPKG STRUCTURE*
To encourage more high‑quality packages in the registry, here’s how I can help you, step by step:
1. You create the Git repo on any supported host (MQL5Forge, GitHub, GitLab, or Bitbucket) and push your existing MQL code there.
2. You send me a private message on MQL5 with the repository URL and a short note that you’d like it adapted for KnitPkg.
3. I will fork your repository, adjust the structure and manifest to match the recommended KnitPkg project layout, and open a Pull Request with the changes.
4. You review and merge the Pull Request into your repository.
5. With the structure in place, you publish your project to the KnitPkg registry by running this single command on your machine: 'kp register'. After that, your package becomes installable by any developer using KnitPkg, via a simple:
$ kp add @yourorg/yourpackage
$ kp install
*DISCOVERABILITY: YOUR CODE IN THE KNITPKG WEB REGISTRY*
Once your repository is published in the KnitPkg registry, your package will be easily searchable through the web interface:
For MQL5 projects: https://registry.knitpkg.dev/mql5
For MQL4 projects: https://registry.knitpkg.dev/mql4
Other developers will be able to discover your work by organization, package name, author, license, or project type, and install it directly into their own MetaTrader projects.
*WHY THIS MATTERS*
MetaTrader projects often grow through copy/paste and ad‑hoc folder sharing. By turning your libraries into versioned packages:
- Other traders and developers can reuse your work reliably.
- You gain a clear distribution and update channel for your code.
- The MQL community moves toward modern, reproducible workflows, similar to what JavaScript, Python, and others already enjoy.
If you’re interested, just send me a private message with your repo link and I’ll help you bring your library into the KnitPkg ecosystem.
Let’s make MQL development more modular, shareable, and professional—together.
· 1
Douglas Nascimento Rechia
Published article Package-based approach with KnitPkg for MQL5 development 
For maximum reliability and productivity in MetaTrader products built with MQL, this article advocates a development approach based on reusable “packages” managed by KnitPkg, a project manager for MQL5/MQL4. A package can be used as a building block for other packages or as the foundation for final artifacts that run directly on the MetaTrader platform, such as EAs, indicators, and more.
779
Douglas Nascimento Rechia
KnitPkg 1.0.0b4 is out 🎉
The big news: you can now install KnitPkg directly from PyPI and keep it updated via pip. This makes it much easier to get started and stay on the latest beta.
👉 Install instructions (PyPI): https://docs.knitpkg.dev/installation/#option-b-pypi
#KnitPkg #MQL5 #MetaTrader
The big news: you can now install KnitPkg directly from PyPI and keep it updated via pip. This makes it much easier to get started and stay on the latest beta.
👉 Install instructions (PyPI): https://docs.knitpkg.dev/installation/#option-b-pypi
#KnitPkg #MQL5 #MetaTrader
· 1
Douglas Nascimento Rechia
Hello MetaTrader developers — I'm excited to share the launch of KnitPkg, a modern, Git‑first package and project manager for MetaTrader 4 and 5 that brings an npm‑like workflow to real MQL development.
KnitPkg models reusable libraries and runnable projects with an explicit manifest, resolves SemVer ranges against Git‑backed sources (GitHub, GitLab, Mql5Forge, and others), and writes a lock file so installs are deterministic and reproducible across machines and CI.
It sits alongside your existing tooling, automates installs and compile steps, and is MIT‑licensed and free for the MQL community.
Your feedback is very welcome — please visit our website, install the tool, and follow the Getting Started guide to try it out. Let's strengthen the MetaTrader developer community with more robust, versioned, and repeatable workflows.
🔗 Home page: https://knitpkg.dev/
📘 Getting Started guide: https://docs.knitpkg.dev/getting-started/
#KnitPkg #MetaTrader #MQL #OpenSource #DevTools
KnitPkg models reusable libraries and runnable projects with an explicit manifest, resolves SemVer ranges against Git‑backed sources (GitHub, GitLab, Mql5Forge, and others), and writes a lock file so installs are deterministic and reproducible across machines and CI.
It sits alongside your existing tooling, automates installs and compile steps, and is MIT‑licensed and free for the MQL community.
Your feedback is very welcome — please visit our website, install the tool, and follow the Getting Started guide to try it out. Let's strengthen the MetaTrader developer community with more robust, versioned, and repeatable workflows.
🔗 Home page: https://knitpkg.dev/
📘 Getting Started guide: https://docs.knitpkg.dev/getting-started/
#KnitPkg #MetaTrader #MQL #OpenSource #DevTools
· 1
Douglas Nascimento Rechia
Added topic Standard library bug in CArrayString::Save(...)
Hi, I think I've found a bug in CArrayString::Save , please see the attached script. You'll notice that only the first string added in the array is saved, loaded and printed. However, after the modification below in
6