AMLEO is a source code complexity mangement tool.

What does AMLEO stand for?

AMLEO stands for Amur Leopard, critically endangered spicies that is close to extinction.
There are a couple of organizations that help protect Amur Leopards:

• Far Eastern Leopards, non-government organization
• Land of the Leopard, Russian national park where cats live

If you like AMLEO tool, please, donate here to help save Amur Leopard from extinction.
We don't ask money for ourselves. We have job. The cats have neither jobs, nor goverment to
protect them. It's our human duty to save diversity of the world.

How can AMLEO help me regain control over my source code?

Do you remember the feeling when you first start coding? Everything is clean, the structure is
beautiful. However, over time constraints start to accumulate and once you have 100+ files, you
lose control of your source code: you forget where to look for certain functionality, you use
search to find out if this or that particular file is the one you're looking for, and so on.
You try to use patterns to keep control of the code base, however, with over 100+ files the
patterns only solve it so much.

The problem is not in patterns, but in the size of the code base. When you have 100+ files,
you simply lose track of what is what and where.

We propose to use so-called staged development together with AMLEO to isolate source code in
chunks called stages with limited functionality.

TODO

• CLI arguments
• Configuration file (Variants.txt) lists variants
  • without extensions
  • allows to enable/disable by using #
• Template files (templates/)
  • define indentation for variants to be inserted

Checklist:

• detect enabled / disabled variants
• detect absent variants
• detect absent variant parts
• merge parts coming from different stages for the same variant (not advised)
• override parts from different stages (strongly not advised)