How to achieve complete autonomy

[Codereamp]

Hi,

thanks for this reveal.js modification. Actually what I'm asking is probably not an issue.

Your solution is closest I found to local/offline requirements I need for a reveal.js presentation. Your demo is working locally but needs online, this is expected as you described. The next step that partially worked was using the excellent SingleFile extension to save your presentation in a single file. The result partially worked (offline html viewer on an android tablet), the slides were switchable, but there are obstacles also, mostly about dynamics inside the slide (no bullet lists, no tabs), also some other issues.

I'm not asking to fix all those issues, but maybe to point to some direction or to append some hints (with disclaimers) in your doc for those who wants achieve full autonomy. BTW, trying to save some pure reveal.js presentation with SingleFile (like this one ) led to a fully unworkable example, so your variant is really step in the right direction

Thanks

[Codereamp]

Actually there's also one point for SingleFile saving. My semi-successful attempt was made when the presentation was on the second slide ("Content .... Press the "F" key to enter Full ") and the state is somehow is saved in this case so the autonomic-version jumps from this slide to the first and then at least allows switching between the slide. But if one saves it while being at the first slide then the slides are also switchable but the first one is never hidden.

So probably the drawbacks and obstacles are too many to easily fix. Anyway, as an expert you might still have some hints to share. Thanks

[dpilafian]

This project does not contain any code to explicitly change or save the state of the presentation.

I'm not aware of the "save" feature you are using. How are you invoking the feature?

[Codereamp]

@dpilafian, sorry for the confusion. I will try to explain what I mean with details

• The original reveal.js is not very local friendly so I could not easily prepare an online version of sites to be correctly played locally (for example by saving a page). So probably that's why your fork was born.
• As you explicitly stated, reveal.js-local is local but not offline-friendly so it requires online for obtaining necessary resources.
• As an experiment I tried to achieve reveal.js-local-offline using the mentioned browser tool - SingleFile, so after having your demo available locally, I saved it with this tool. It basically embedded all the necessary resources with the data uri scheme. And this experiment partially worked so I had your reveal.js-local demo played from scratch on an offline android tablet (with the caveats I mentioned).
• So I thought that since you were able to overcome the obstacles to the local-friendly result, you might also prepare a semi-ready version for offline-also result where one just have to replace dummy references with the real ones (to local js and css files). You were the one who I addressed because in the path to local/offline you already made it half way (local). And probably some expertise is needed because this "made with a extension" result was half-baked so having correct locally referenced presentation is probably a better way than data Uri embedding.