Discuss Scratch

manwithmanykids
Scratcher
67 posts

Whats the best way to Handle Revisions in SCratch

I created a simple Pokemon Game to see what I could do with Scratch.

http://scratch.mit.edu/projects/10368996/

Once it was created, I wanted to start improvments to it, but leave the current version incase I wanted to go back to it for what ever reason so I created a copy of the original, added features and eventually shared it.

http://scratch.mit.edu/projects/10410427/

Next I decided I wanted more options, so again I Copied it and made updates.

http://scratch.mit.edu/projects/10433760/

I now have 3 Versions of my project which I have named V1, V2, V3.

My question is, what is the best pratice for maintaining revisions? I am very new to scratch, but a long time coder in other languages, so I am used to have several revisions of code and working on several projects at once. I Noticed the Remix option. If that the route I should have taken?

Any one with thoughts or suggestiond please feel free to respond


Heres my Pokemon Battle Project

http://scratch.mit.edu/projects/10433760/

Harakou
Scratcher
1000+ posts

Whats the best way to Handle Revisions in SCratch

I think whether or not you choose to use remixes as a sort of versioning system would be up to you. If you have a lot of versions, it would have the advantage of giving you a nice hierarchy. There's even a nifty remix tree feature, so if you have a couple different variations of one version, you could see the different branches.
manwithmanykids
Scratcher
67 posts

Whats the best way to Handle Revisions in SCratch

Thanks

Heres my Pokemon Battle Project

http://scratch.mit.edu/projects/10433760/

Powered by DjangoBB