share scenario button / basically, allow scenario to be encoded in URL about gloom HOT 6 CLOSED

I see what you are saying. Encoding the scenario in a URL, to allow sharing, is a very good idea.

from gloom.

What are the advantages of that approach?

How does your code slot into the functions storeState() and restoreState()?

from gloom.

Well, storeState() and restoreState() work only locally in your browser.
The lines above* can be used to export to a (long) string and import from that, to present to the user and thus traverse browsers and computers.

(* They are untested, and maybe not very efficient or elegant, but should do the trick)

I am just setting up a flask environment to take a look at the system myself, maybe I can propose a pull after all

from gloom.

This could be used to crowd-source the scenario implementations. You can curate a bookmarked URL list that will load each scenario, room by room. Once someone trustworthy has validated the URL does correspond to the scenario, it can be added under a new Bookmark button or something in the app itself for everyone to use.

from gloom.

Agreed. This can be a powerful feature. Got me excited enough to pick the project back up again.

I did a test of the naive solution, and unfortunately it resulted in 10K URLs. I've got something more sophisticated working. Need to add validation and clean it up. Soon.

from gloom.

Great idea! Feature added at fb27077.

Deploying now.

from gloom.