Upgrading the doc, the readme (or the wiki) #12
Description
After a couple hours of using this framework, it appears that some concepts are low documented.
Even with the included smoking example to show one usage (and even more, this included example is counter productive, I think).
Maybe first, I explain how I see this things; I distinguish 3 personas: the person developing the framework, the person configuring a certain installer, and the person running the installer.
Since the locations in code for configuring are nearby the code made by the framework developer, it's hard to see what is editable, and what not to touch.
I saw in comment the idea of using callbacks... this could have been a good architecture concept, to avoid mixing this 2 things in the same file, and maybe to locate all editable files in the same directory.
What files are containing the tailored installer (I think tasks, config...)?
Same major and traditional aspect of an installer are missing.
Complete/incomplete states appear like a major concept. But to me who uses other frameworks, this is not.
But other concepts like first install, update mode, uninstall... are missing.
Is it possible to have 2 installers bundled in one? (separated product 1, product 2 not disturbing each other)
This remarks are very incomplete, I know.