Housekeeping for 0.7

[jamwaffles]

Progress towards #8 and #5, closes #7, closes #6.

[jamwaffles]

Rectangle intersection moved to embedded-graphics/debug-tools#9.

[jamwaffles]

A bit of a kitchen sink PR, but I think I've covered most points in the other issues in this repo

[rfuest]

Closes #8, closes #7, closes #6, closes #5

8 still need some work after this PR is done.

And this PR is a good start towards #5, but could also use some work. Should we also add licensing information to the readme?

[rfuest]

• Should we move simulator-input-handling to the examples directory in the simulator repo?
• Should we rename line-thickness to primitives-line-thickness or also move it debug-tools?
• Can we set the initial progress value in demo-progress to something != 0? This would make the screenshot more interesting.
• text-custom-font will need to be fixed after the next beta release.

[jamwaffles]

To address your points in order:

1. Agreed, that example really doesn't make sense here does it. Moved in embedded-graphics/simulator#26
2. I've deleted it, as we already have the line debug tool which does the same thing AFAICS.
3. Set to >0 now, looks better indeed.
4. :+1:

As for the licenses, I can use the same structure as the e-g repo. Let me do that quick...

[jamwaffles]

Licenses are added, MIT or Apache 2.0 the same as e-g. I also added them to the Cargo.toml of each folder which isn't really necessary, but can't hurt.

[rfuest]

Some final comments:

• I would prefer to keep the analog prefix for the clock demo, because I'm considering to add a eg-seven-segment based digital clock example to this repo: https://github.com/embedded-graphics/eg-seven-segment/blob/master/examples/digital-clock.rs
• IMO primitives-ellipse and primitives-rounded-rectangles are debug tools. Should we remove them? Both primitives are used in other examples.
• The comment in text-fonts says: "Demonstrate the available builtin fonts." We should either change the comment to state that this is a subset of available fonts and a full list is included in the docs or add all fonts to the example. I guess the first solution would be easier to implement and maintain in the future.
• text-extended-characters: The comment needs to be updated, because all builtin fonts support the characters in this example

[jamwaffles]

Changes addressed :)

[rfuest]

Should we "fork" the eg-0.7 examples directory in this PR? Because the Cargo.toml in eg-next was supposed to always use git dependencies.

[jamwaffles]

Ah, no, I think we should do that when 0.7 is released. Technically there's no proper release yet, so keeping eg-next as is for the short term makes sense to me. I've reverted the dependency changes back to the git/patches for this PR.

[rfuest]

OK. But I have to admit that finally seeing the Cargo.toml without any git dependencies looked really good.

[jamwaffles]

Thanks for the reviews! These examples look really good now.

But I have to admit that finally seeing the Cargo.toml without any git dependencies looked really good.

It did look spectacular! The quicker we can get the migration guide done the quicker we can release non-beta and go back to non-Git Cargo.toml utopia ;)