Demo where steps can be set via URL hash

[jywarren]

So it looks in window.location.hash to find a comma delimited set of steps, like #steps=ndvi,threshold, and adds them to the reconfigurable demo.

As you remove/add steps, we update the URL hash to reflect this.

That way, we can pass around almost any imaginable demo sequencer as a fixed URL -- very useful!

This would come after #82 (completed!). Some example of reading/writing the URL hash can be found at https://github.com/jywarren/fisheyegl/blob/master/example/urlHash.js

[jywarren]

So, for example, if someone says "I wish there were a fast way to crop and threshold these images", you could send them a link to the demo with the right steps configured, and they'd go and it'd be all set up for them, with no having to change the demo code :-)

[ccpandhare]

Yes, I agree to this. I shall do that. Now working on #82 :-)

[jywarren]

awesome!

[jywarren]

This will be great. I think we can even embed a customized sequencer into a wiki page or research note on PublicLab.org -- it'll be a great way to put the library into use!

[ccpandhare]

Hope to do that soon :-)
Will get the demo done by tomorrow, and then we can work on this (#91) and then the wiki page!
This will be good documentation too.

[ccpandhare]

The demo is pretty much done for now, so I shall start working on this

[jywarren]

Great. Sorry for being offline much of this week, it was a vacation I really needed! I'll be back online this coming week.

[ccpandhare]

What if the user wants to set any options? I think that should be included in the hash as well.

[jywarren]

Sure, but then the hash may get pretty long. Let's see how it does though. Maybe we can either offer to save the options with a checkbox or we can just clearly label options so they can be cut out of the URL if people want. But yes let's start by including them. Good idea!

…

On Aug 20, 2017 8:54 AM, "Chinmay Pandhare" ***@***.***> wrote: What if the user wants to set any options? I think that should be included in the hash as well. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#91 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJ66kIJ04v-uFzclU3S13n_inwv09ks5saCxxgaJpZM4Ozae7> .

[jywarren]

should we add a distinct button called "generate permalink" to this? Or is it clear?

[ccpandhare]

This is pretty clear.
I am just skeptical about adding options to steps via the hash, and if we don't, the incompleteness of the same.

Yes, we should start including them.

[jywarren]

What do you think about a syntax more like:

examples/#steps=ndvi,threshold[40] -- although this starts to get a bit weird, and we'd have to specify the keyname too, so [value=40] ... just brainstorming here.

[jywarren]

also I added you on npmjs.org - you should be able to npm publish now, but please take care to do so only from the master branch.

[jywarren]

Now that I think of it, let's just break this in two. First version should have just steps, no options. It'll just use the defaults. Let's open another issue (which we can think about a bit longer) that has options presets too. That more extended version shouldn't stop us from doing the initial version first.

[ccpandhare]

Looks cool. Will do!

[jywarren]

Completed and split off new issue!