v0.3.0?

[Tymewalk]

When do we want to release v0.3.0? And what do we want added before then?

[Tymewalk]

I know #42 is on the list, as well as resolving #49. Anything else I may have forgotten?

[Tymewalk]

Bumping this. Slither development has been dead for a while but I'm working on fixing that. See #58 for what I'm doing right now.

[Tymewalk]

So, #59 is having some problems that I'd like to fix by releasing 0.3.0.

Does anyone know of anything that should get done before then?

[skistaddy]

I believe #59 just got solved, so isn't 0.3.0 ready to release? Maybe add URL image support?

[Tymewalk]

I believe #59 just got solved, so isn't 0.3.0 ready to release?

Yeah, #59 was resolved, although that has nothing to do with making 0.3.0 ready to release (I originally wanted to release it so PyPi would stop complaining about the 0.2.x versions, but it's fine now.)

Maybe add URL image support?

What do you mean by that? Do you mean getting images from the web and adding them to a Slither project?

[skistaddy]

It would be the Same as adding a vector image, just through a URL.

[Tymewalk]

It would be the Same as adding a vector image, just through a URL.

I'm still confused. Do you want to get an image from a URL like "http://imagehost.com/blah"?

[skistaddy]

Yeah. So instead of using a file it uses a URL

[Tymewalk]

Yeah. So instead of using a file it uses a URL

Sounds cool, but couldn't that open up security vulnerabilites? I've heard of things being hidden in images and opening up every Slither script to something like that isn't good.

[skistaddy]

True. And Scratch doesn't support that either, so best not to add it.

[Tymewalk]

True. And Scratch doesn't support that either, so best not to add it.

I don't think that last part is true (although I'm not saying we should add this). Just because Scratch doesn't support something doesn't mean it shouldn't be added.

[skistaddy]

True. And Scratch doesn't support that either, so best not to add it.

I don't think that last part is true (although I'm not saying we should add this). Just because Scratch doesn't support something doesn't mean it shouldn't be added.

It is supposed to be a module for Scratch, yes?

[Tymewalk]

True. And Scratch doesn't support that either, so best not to add it.

I don't think that last part is true (although I'm not saying we should add this). Just because Scratch doesn't support something doesn't mean it shouldn't be added.

It is supposed to be a module for Scratch, yes?

Not really. It's supposed to bring Scratch-like features to Python. I also intend for it to make things in PyGame easier for beginners, and also take advantage of features in PyGame that don't exist in Scratch.