I think he/she means that the new blank project gets autosaved (this is an issue for me, too).

Hardmath123
I think he/she means that the new blank project gets autosaved (this is an issue for me, too).

That's what I'm saying: blank new projects are not “autosaved.” When you click “Create,” your browser goes to http://alpha.scratch.mit.edu/projects/editor/. There ScratchR creates a new, unshared project and redirects you to the project's editor page (e.g. http://alpha.scratch.mit.edu/projects/10012655/#editor). By the time you reach the editor, the project has already been created. It doesn't autosave until the project is modified.

nXIII

ka-doink4545o0
Auto-save spams up my projects with Untitled-number every time I click Create, then think, “Oh wait, wrong button.”

That's not autosave, that's the way the create button works.

Actually, it is autosave.

Firedrake969
Actually, it is autosave.

No, it's not.

ka-doink4545o0
Auto-save spams up my projects with Untitled-number every time I click Create, then think, “Oh wait, wrong button.”

Ah, that's actually a re-introduced bug. If you hit create, and don't make any changes, then it doesn't make sense to store the project since it contains no data. Not really autosave, but related to it certainly. I'll ask John to look into this when I see him.

Lightnin wrote:

Yep, this is a weakness in our current implementation in that we autosave, but don't provide a list of “versions” in case you want to revert to a previous save.

However - autosave has a lot of advantages for new users, so as a strategy I think it is sound. After all, the real world is “autosave.” If you rearrange a stack of blocks, you don't need to hit save - they're just there.

Once we add a revision list, it should solve most of the problems you guys are experiencing. That is - if you tinker around and don't want to keep your changes, it should be easy to revert.

It'll take more technical users more time to get used to (because we're used to saving). But of course our main goal is to support non-technical users.

when exactly do you intend to create this? the main thing that's preventing me from branching out into larger projects on 2.0 if the fact that everything saves when I don't want it to. ive has several mishaps already where things were deleted and the project saved itself, so i had to remake them.

Wes64 wrote:

Lightnin wrote:

Yep, this is a weakness in our current implementation in that we autosave, but don't provide a list of “versions” in case you want to revert to a previous save.

However - autosave has a lot of advantages for new users, so as a strategy I think it is sound. After all, the real world is “autosave.” If you rearrange a stack of blocks, you don't need to hit save - they're just there.

Once we add a revision list, it should solve most of the problems you guys are experiencing. That is - if you tinker around and don't want to keep your changes, it should be easy to revert.

It'll take more technical users more time to get used to (because we're used to saving). But of course our main goal is to support non-technical users.

when exactly do you intend to create this? the main thing that's preventing me from branching out into larger projects on 2.0 if the fact that everything saves when I don't want it to. ive has several mishaps already where things were deleted and the project saved itself, so i had to remake them.

Branching and merging is pretty easy already—save a copy, then export->import to merge.

How about instead we have a choice in case someone wants it.

nXIII wrote:

Mokat wrote:

You should be able to turn it on and off.

I don't agree. Autosave prevents users from losing any of their work, and that's very important for new Scratchers and helpful for more experienced ones. If you have versions available to you as well, you can revert to a previous version of the project, so you will never lose work by making changes, either.

What would be useful for me is to be able to declare a certain version of a project as the shared version and continue working on that project without further changes being shared.

You didn't read that at all.

nXIII wrote:

Hardmath123 wrote:

I think he/she means that the new blank project gets autosaved (this is an issue for me, too).

That's what I'm saying: blank new projects are not “autosaved.” When you click “Create,” your browser goes to http://alpha.scratch.mit.edu/projects/editor/. There ScratchR creates a new, unshared project and redirects you to the project's editor page (e.g. http://alpha.scratch.mit.edu/projects/10012655/#editor). By the time you reach the editor, the project has already been created. It doesn't autosave until the project is modified.

If you leave the page, though, it won't delete the thing. It just puts it in the Trash section (which I find annoying, so I created a project designed solely for experimentation).

Wes64 wrote:

when exactly do you intend to create this? the main thing that's preventing me from branching out into larger projects on 2.0 if the fact that everything saves when I don't want it to. ive has several mishaps already where things were deleted and the project saved itself, so i had to remake them.

Probably not before the release, but hopefully not long after.
Have you tried the “Revert” function in the file menu? That's the proposed stop gap for the issue.

lalala3 wrote:

nXIII wrote:

Hardmath123 wrote:

I think he/she means that the new blank project gets autosaved (this is an issue for me, too).

That's what I'm saying: blank new projects are not “autosaved.” When you click “Create,” your browser goes to http://alpha.scratch.mit.edu/projects/editor/. There ScratchR creates a new, unshared project and redirects you to the project's editor page (e.g. http://alpha.scratch.mit.edu/projects/10012655/#editor). By the time you reach the editor, the project has already been created. It doesn't autosave until the project is modified.

If you leave the page, though, it won't delete the thing. It just puts it in the Trash section (which I find annoying, so I created a project designed solely for experimentation).

Yeah, it should probably just completely delete projects if there's absolutely nothing in them.

Lightnin wrote:

Wes64 wrote:

when exactly do you intend to create this? the main thing that's preventing me from branching out into larger projects on 2.0 if the fact that everything saves when I don't want it to. ive has several mishaps already where things were deleted and the project saved itself, so i had to remake them.

Probably not before the release, but hopefully not long after.
Have you tried the “Revert” function in the file menu? That's the proposed stop gap for the issue.

i didnt see that, thanks!

Mokat wrote:

You should be able to turn it on and off.

That would be a great idea… However, the Account Settings page has not been finished yet.

Laternenpfahl wrote:

Revivions.

Please

OMG! My project is dead! ST, we must revive him!

jk

lalala3 wrote:

Mokat wrote:

You should be able to turn it on and off.

That would be a great idea… However, the Account Settings page has not been finished yet.

Speaking of which, they need to do so.

nXIII wrote:

Mokat wrote:

You should be able to turn it on and off.

What would be useful for me is to be able to declare a certain version of a project as the shared version and continue working on that project without further changes being shared.

Yes for this.

Wes64 wrote:

when exactly do you intend to create this? the main thing that's preventing me from branching out into larger projects on 2.0 if the fact that everything saves when I don't want it to. ive has several mishaps already where things were deleted and the project saved itself, so i had to remake them.

That's happened to me too… It's so annoying

I don't get why there can't be a button to toggle auto-save. Or, maybe there could be backups along with the auto-saves.

Tierage27 wrote:

I don't get why there can't be a button to toggle auto-save. Or, maybe there could be backups along with the auto-saves.

I think there should be both, by making an option with three settings: Don't autosave, rename autosaved file (default), and replace original file.

Is there anything wrong with giving people options in life?