I'm not often using the backpack.
But sometimes, when i make a new project, i want to import a script from another of my projects.
So, i open a new tab without quitting the editor of the project I'm making. Then, i search for my script in my projects. When it's done, i add it to my backpack.
After that, i come back to my editor tab and open the backpack. But it's content isn't updated, i have to refresh the page to get my scripts…
This is quite annoying for a few reasons :
- When you're updating a shared project, you don't want to save the changes until the update is fully done, but you have to if you refresh your page.
- When you're doing a big project, you don't want to forget the place where you are modifying something, but when you refresh, you have to find it again in the editor.
-When you're working on a heavy project, you don't want to load the data many times
That why i suggest to make the backpack being more reacting to changes in a way to make it upgrade without needing to refresh pages.
How ?
A solution would be to update the content of the backpack when you open it. By this way, the only thing you would have to do to refresh your backpack would be to close it and re-open it
And it would be easier to implement compared to a constant update of the content
Za-Chary
Semi-support.
I totally understand what you're getting at. I refresh the page all the time when I'm trying to make projects with the backpack. It would be nice if the backpack was some sort of real time thing.
However, I am worried that it may be too much work to implement for something that doesn't really matter for Scratch. Are there any other “real time” things on the Scratch website (not in projects), that get updated without needing to refresh the page? Perhaps it is something that the Scratch Team has not tried doing before.
I totally understand what you're getting at. I refresh the page all the time when I'm trying to make projects with the backpack. It would be nice if the backpack was some sort of real time thing.
However, I am worried that it may be too much work to implement for something that doesn't really matter for Scratch. Are there any other “real time” things on the Scratch website (not in projects), that get updated without needing to refresh the page? Perhaps it is something that the Scratch Team has not tried doing before.
bidulule
For example, messages are updating without screen refresh. Semi-support.
I totally understand what you're getting at. I refresh the page all the time when I'm trying to make projects with the backpack. It would be nice if the backpack was some sort of real time thing.
However, I am worried that it may be too much work to implement for something that doesn't really matter for Scratch. Are there any other “real time” things on the Scratch website (not in projects), that get updated without needing to refresh the page? Perhaps it is something that the Scratch Team has not tried doing before.
Aslo, a solution would be to update the content of the backpack when you open it. By this way, the only thing you would have to do to refresh your backpack would be to close it and re-open it

And it would be easier to implement compared to a constant update of the content
Za-Chary
Hmm…that is true. Your proposed idea about refreshing when you open the backpack is a good idea.For example, messages are updating without screen refresh. Semi-support.
I totally understand what you're getting at. I refresh the page all the time when I'm trying to make projects with the backpack. It would be nice if the backpack was some sort of real time thing.
However, I am worried that it may be too much work to implement for something that doesn't really matter for Scratch. Are there any other “real time” things on the Scratch website (not in projects), that get updated without needing to refresh the page? Perhaps it is something that the Scratch Team has not tried doing before.
Aslo, a solution would be to update the content of the backpack when you open it. By this way, the only thing you would have to do to refresh your backpack would be to close it and re-open it
And it would be easier to implement compared to a constant update of the content
I still have to say semi-support, because I worry it still might take a while to implement, again, for something that isn't largely important. You do have some great ideas, though.

bidulule
Thks dude
YubNubEwok
Total support!
I had been working on a collaboration a while ago, and not having my backpack refresh was SUPER annoying because whenever I would refresh my page, then it would take a little bit to load.
I had been working on a collaboration a while ago, and not having my backpack refresh was SUPER annoying because whenever I would refresh my page, then it would take a little bit to load.
bidulule
Total support!
I had been working on a collaboration a while ago, and not having my backpack refresh was SUPER annoying because whenever I would refresh my page, then it would take a little bit to load.

duckboycool
Support, not a particularly large issue, but it can be annoying. And I definitely agree with the points you mentioned there.
NilsTheBest
Support ^^
It would facilitate exchanges between projects for sure, if we're on a complicated project with lots of scripts and we don't want to get lost.
It would facilitate exchanges between projects for sure, if we're on a complicated project with lots of scripts and we don't want to get lost.
bidulule

YubNubEwok
Hahahah, that's really creative!
bidulule
AlwaysHahahah, that's really creative! Something

Sheep_maker
From here:
This may imply that Scratch 3.0 already has this feature. It loads content when the backpack is toggled
bidulule
here:great then! FromThis may imply that Scratch 3.0 already has this feature. It loads content when the backpack is toggled
paws48
Support! It would be useful, and it couldn't be too difficult to implement.