Version 1.0

[BookOwl]

What do we need to have done before we can go to 1.0?

[Tymewalk]

First we need examples, plus more up-to-date docs.
Next I think we need to decide what we're going to do with pen (#23) and SVG support (#35).
Also better sensing (collisions are in #42).

[emmatyping]

Do you want feature parity by 1.0? Or is that for later or not planned?

[Tymewalk]

Do you want feature parity by 1.0? Or is that for later or not planned?

What's that?

[emmatyping]

Sorry, feature parity means that we support all the same functionality of Scratch. So one could port to Python from Scratch any project theoretically? Or are we aiming for a subset of the Scratch functionality?

[Tymewalk]

@ironmanmark20 Hmm... the events like "when I receive" are tricky. Although yes, most features will be included.

[Tymewalk]

Clarification.

By 1.0.0, all or almost all features of Scratch should be replicated in Slither.

It should be possible to take just about any Scratch project and rewrite it in Slither without too much effort.

This doesn't mean we'll just add everything - variables, control loops, etc. will not be included in Slither since they're already in Python. Remember - the goal is to make Python more like Scratch, so new users can get used to Python's format.

There will also be some convenience functions specifically related to PyGame/Slither (see #62 for an example of this).

A slither wrapper for Tkinter would be awesome! ;)