Issue 99 documentation

[danwood]

Description

I put in documentation comments for just about all structs, methods, etc. There are just a few pieces that I didn't mess with because I don't really have a good understanding of it to give a good explanation - maybe Andris can fill in the blanks? I really didn't get into Path+QuadCurve.swift for instance - the author will understand what is going on much more than I can. A few other pieces I couldn't figure out how to document - look for <#Description#> and <#content description#> in the code. (Still, everything builds fine, it could get merged in even with these pieces incomplete.)

Motivation and Context

See issue 99

How Has This Been Tested?

No code changes (except a couple of tweaks to make public/private consistency). It builds fine.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (Updating Documentation, CI automation, etc..)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[AppPear]

awesome work i will also fill in some details