Yes, I guess you are right. But I could assign the content of the default xml file to a variable and then run an "open" command somewhere with that variable as an argument?
Local files access is more and more restricted. Even if you manage to lower some restriction with the cmd line flags, the next browser version may ignore those settings.
.
Or, Jens can expand the "-snap-backup-" idea to store default projects in local storage.
.
Snap: source code and media files have been whitelisted for offline use (sw.js). Maybe a some projects URIs can be stored, this way, too.
.
How deep is your offline mode? You want the whole to run from disk (allowing you to make your own version)? Or can run a shared LAN server?
Or use the SnaPP! way to bundle the and the project as a standalone app.
Yes I know, it's currently outdated and does not work with the v8 projects...
There is an interesting option "Code accessible" that could be important to me (I'm implementing an introductory pseudo-language for high-school students). But, as you said, I got this error message:
I wanted to know because I think I have a solution that requires editing the source code a little bit. The good news is that you happen to be using the downloadable ZIP.
For chrome:
Just open a new Snap! instance, click on the three dots:
I didn't know about this possibility (I started using Firefox two years ago for problems of Chrome with specific websites I use a lot). Do you know if there are advantages with respect to downloading the source files?
For a split second I thought this could be the perfect solution: when I installed Snap after opening the project I need as a defult, it showed me the Snap! webapp with the project open inside. But then, when I closed the app and reopened it, the project was gone
Before anyone says anything about my use of install, I said install, but meant "Create Shortcut". "Create Shortcut" is probably the solution to what you're looking for (in Chrome/Chromium-based services), and you can find it under "More Tools" when you press the three dots.
To my knowledge, when you open an installed app/thing/site it opens whatever link you installed. Pressing the install button on Snap! Build Your Own Blocks will result in always opening that window. However, if you install the Snap page with a public or shared project open in editor mode (it has a different link) it will install that.