Cameyo

As the subject says. I feel it would help everyone make better apps if we knew how the engine worked. I'm not saying release a source code, but generalize the steps it makes.

Something like:

-the first thing it does is copy x files to y

-then it does z

This way we can see how apps fails to work and what is causing it to fail and at what step. 

The main reason I am asking for this is because the Documentation looks like very little info was put into it. I very often find myself wondering if I am doing something correctly or wrong. If you want a good example of how Documentation should look like, let me point you towards the AutoIt3 Help File Link.

Like ok I want to -fullintegrate my app but no shortcuts are made because I manually deleted their entries in the package editor. How do I add them back? There is no documentation for -FullIntegrate except for the small paragraph letting you know it exists. How is this helpful? I understand you documented the function, but still, you should as the developer of the software you release, explain how a function works.

I have tried many different solutions for portable apps and this seems the most promising. Vmware Thinapp works fine but not on Windows 10. PortableApps Format worked but cleanup was slow and you had to follow a set directory structure and was a pain to use. Cameyo doesn't have any of these problems, but it's documentation is lacking. 

Ok enough complaining about how its difficult to use your software. What will you do to remedy this? Are you going to rewrite the documentation? Explain the engine? I await your answer.