

Of course that's possible! Like essentially all programming languages, Scratch is Turing-complete.
#Scratch to snap converter code
All of the graphics parts of your code could be replaced by pygame function calls. (Note: This doesn't mean that what the project does couldn't be done in Scratch using a different algorithm. You could use CoRo Scratch by BookOwl it should transpile your scratch project to python. But users who have an adventurous spirit will soon start writing projects that couldn't be translated. scratchOpcode is the opcode of the Scratch block, or None if there is no Scratch equivilant. When people familiar with Scratch first try out Snap !, they (understandably) start by making projects that could be translated to Scratch if someone wanted to build a program to do it. snapSelector is the identifier Snap uses to identify the block.

These things are what motivated us to create Snap ! in the first place.

Remove dust and scratch marks from bitmaps Sharpen images. Scratch projects can mostly be translated to Snap ! using Snapinator.Ĭertain Snap ! features that aren't in Scratch but easily could be can be translated using Scratch custom blocks, but there isn't a program to do that because the core features that make Snap ! different from Scratch can't be translated: first class procedures (indicated by gray rings), first class lists (for example, making a list of lists), and first class sprites with inheritance (cloning Scratch does have something that looks similar but their clones are copies, whereas our clones share data and methods with their parent). Position objects Align and distribute objects Apply object hinting Snap objects.
