[k2enemy]

Very cool. Just a suggestion for the demos in the README though. Maybe have the code shown statically, then a gif of the GUI. Watching all the typing gets long when I just want to see the resulting GUI.

[kirstenbirgit]

Yep, there's zero reason for the gifs. They seem really slow to me. Makes it impossible to copy the code if I wanted to, as well.

[sbarre]

The code is on the page, in text, directly below the GIF, if you want to copy it.

The GIFs help, they should just start with the code getting pasted in, not typed in.

[nfin]

and clicking the gif gives you a skippable video

[zapzupnz]

Taking me to another website to look at the same clip — and then make me skip to the end myself and then manage having to pause the video — is lipstick on a pig.

A JPEG will be just fine.

[azinman2]

Except there are several videos and no need for me to click each one to find out what the output eventually looks like.

[oefrha]

Also, move at least one screenshot/cast to the top, not after tons of technical documentation.

[rjstelling]

Thanks for the feedback, I've improved the Readme file and broken it into several pages.

I'm also going to add shorter videos at the top.

[zapzupnz]

Not shorter vids. Pictures.

[azinman2]

I'm fine with a gif.. because the whole thing could be like 3 seconds long.

[zapzupnz]

The only thing we need to see is the outputted user interface. Everything else is superfluous.