Saving changes made in the Application!

pontus wrote:

Is it possible to close the application and save the changes that was made to later open it up again?

You can export changes to GLTF and load this GLTF later…

I think what you are looking for is something like a “resume” feature that reloads the user app to the exact same state it was before closing the browser.

That would be a VERY nice feature/puzzle to have in Verge. So why don’t we don’t we have it?

Good question.. I for one never really thought much about requesting it as my understanding has always been ‘saving to disc’ means having to configure something to store it in – meaning database setup, php scripting, and other fun stuff that involves coding… Basically, something way out of scope for Verge3d developers to invest time in much less trying to provide user support for.

*Wordpress being the exception here, as its standardized, mainly codeless option for Verge users to be able to ‘plugin’ an online DB storage solution. However, not everyone using Verge uses, or wants to use, WordPress.

So I suppose I had ruled the idea that there could be any EASY button (puzzle) to implement a ‘save to disc’ and ‘resume’ feature for Verge apps… but that was before I learned about window.localStorage

https://www.w3schools.com/jsref/prop_win_localstorage.asp

It is so simple to use and from what I see, it’s a standard feature across all major browsers.

So far, what I have managed to put together is a simple scheme where I create a dictionary with the variables I want to save (as Yuri and company have been advising as a solution for years), then convert it to a string to save to local storage.

When my app loads, it checks localstorage to see if my key is set, if its not there, I run a procedure to set their default values – if the key is set, I load the string value into a JSON to setup a dictionary with the saved values, then run a procedure to set my variables to those values.

Being able to simply save and load variables is great – but, its still far off from being an easy button for a ‘resume app state’ feature.

You basically have to wire another layer of logic into your app to deal with the event of reloading variables and setting things to get back to the saved state where you left off. If your app allows users to modify any properties of objects (position, color, textures, clones etc), then things get even more complicated.

It would be SO nice if Verge developers could come up with something that could essentially take a ‘snapshot’ of an apps current state (variables, object properties, etc) that could then be automatically restored/resumed on command.

Still not sure how technically feasible such a feature would be, BUT with an essentially universal storage option (web local storage) open to all Verge developers (and end users) on the table… I now just have to ask the question to the Soft8Soft team.

Yuri? Your thoughts?

For starters, maybe a “create suspend data string” puzzle that simplifies the process of gathering all variables used in the app and writing their values, along with any object properties, when invoked at runtime, and writing out a stringified JSON formatted text string?

With options to then save that string to local web storage, send to database, or whatever?

Not sure what the puzzle looks like to load/unwrap the info back into the app as part of the resume process, but I am sure you guys could figure something out.

Hi,

Indeed, having local storage supported in Puzzles would be very useful. Making it a priority task.

Regarding SCORM 2004, we should consider adding this standard to Verge3D as well. The strange thing with it, however, I can’t say exactly what open-source LMS-es support this standard. We used Moodle to test our e-learning Puzzles, but the developers of this system stopped working on SCORM 2004 long time ago. Perhaps you have some LMS in mind that you can recommend?

Interesting idea! It’s definitely worth thinking about it

A draft variant of the save/restore system based on GLTF export/import )))
https://v3d.net/9vj
Materials should be MeshStandardMaterial. MeshNodeMaterial is exported as MeshStandardMaterial (glTF 2.0 compatible)

p.s. Four cubes are draggable, two of them are hidable.

Woah!! KDV, that is awesome!!!!

I got pulled away from board and only today came back to this thread.
For others who missed it, check out KDVs demo app which allows for saving an apps state then reloading in the exact same state you left it.

https://v3d.net/a4k

KDV, so using Verge Storage key puzzles, you could basically stuff that ‘.sav’ into a local storage key, and have things setup so when the app loads, it will check for that key, if found, loads and restores the user session? Pretty sweet!! Nice work, thanks for the high quality contributions!!

kdv wrote:

Crunch wrote:

you could basically stuff that ‘.sav’ into a local storage key

No, localStorage is not used. It can store string values only and it’s too small to store some serious scene. All parameters are exported into .gltf file and then restored from it.

That’s pretty impressive! Could you give us mortal non-coders maybe a little bit more to go on? Would it be possible to see the puzzles to try and figure out how you accomplished this?

Thanks!