Scratch

scmb1 wrote:

That would be really cool!  The Scratch Team has plans to have something that sounds like that, but I don't know the details. They wrote that in 2.0 they're considering

3. Providing new features to make it easier for groups and companies to collaborate on projects.

I'm not entirely sure what that means, but it may be like what you want.

That sounds great!


But probably not this. When I got the idea, if felt seriously original. 

I hope they add it!

That would be a great idea. Kind of like hosting a mesh on BYOB, right?

juststickman wrote:

I like this idea....
But how consistent would it be?

For example, if one person pressed the green flag, would it appear for everybody or just them? If just them, that means they could fix a glitch and stuff.

It should appear for just them I think.

Another idea would be using private scripts (perhaps a copy of the project which you can modify so the changes only appear to you) that only runs for you, to test out features to add to the collab. If the script worked well, you can make it public.

Last edited by technoguyx (2010-05-04 23:22:54)

Uh.. Bump...?

We definitely need this, I made a post similar to this idea here

Sure! It's a great idea, one we've been thinking about and discussing for a while now.

It would be *awesome*, but it's very complicated to implement in a way that would work well. We may focus on better "asynchronous" collaboration tools for Scratch 2.0, and save this kind of change for a later version. Asynchronous means tools for collaboration that work in discrete steps - as in I add a little bit and submit it, then you add a little bit and submit it. Maybe we're both online at the same time, or maybe not - it works well either way because the changes happen in "chunks" rather than in "real time."

This is perhaps not quite as thrilling as being able to see the blocks as someone else is moving them.... but definitely more doable.. for now... 

But - if you have a vision of what this might look like, we'd love to see it! Please make a project demonstrating how your system might work / look. These kinds of changes will need a lot of careful thought put into them, so we'd love to have help thinking them through. 

I agree with Lightnin's asynchronous collaboration for now.

I'm curious how you're thinking that should work.

Perhaps: the ability to submit, change and discuss issues (bugs, feature requests) on a project page.
Then, someone can decide to work on an issue, submit those changes in a new project, the original issue is notified, so that others can try out the "patch".
Then the original project owner can easily merge those changes back to the main project?  (with the ability to detect conflicting changes, and assist with merging?)

Perhaps something like Git for kids? 

Last edited by AddZero (2010-05-11 19:02:48)