Hi,
it would be great to add the gui objects of the scene when you save it in the .babylon file format.
Thanks in advance,
Boris
Hi,
it would be great to add the gui objects of the scene when you save it in the .babylon file format.
Thanks in advance,
Boris
Hi!
I don’t believe it’s a good idea to mix the 3d stuff with the gui. However you can save and load your gui using another methods. Watch this great video for more information.
May be you’re right, i’m a beginner in Babylon JS.
But i thought it would be easier to be able to save and load your scene with all elements.
Anyway, if my idea seems to be bad, the developers won’t do it and i totally accept that. I assume that Babylon JS is made for the all community and not only for my own needs.
At least, i think that the documentation has to be completed to know what is saved and what is not.
Boris
Yes, a lot of things needs to be documented but we have always the possibility to have a look at the source code and that’s very valuable in my opinion. if still in doubts the forum users will help for sure. However in this case think of the the babylon file format just as of another 3d file format, like gltf, obj, fbx.
However in this case think of the the babylon file format just as of another 3d file format, like gltf, obj, fbx.
This is is a good away to put it.
I assume that Babylon JS is made for the all community and not only for my own needs.
While this tends to be true and we don’t want to bloat code for specific things, we are open to hearing all kinds of feature requests and suggestions.
Now that the GUI editor is here and people are using it more with the serialization this point is being brought up. I think this prompts a conversation to be had. While gut feeling says that it doesn’t make sense to add it. Let me get back to everyone one this. Regardless, if documentation needs to be updated to make things more clear, I’m all for that! I really like how Roland put it so maybe that’s a good place to start with updating some of the docs.
I am rethinking this and actually @bvaisman gave me an idea. Maybe it would be cool to have a serializer which could store everything in one file. We can think of it as a packager for BabylonJS. You can then share the package which will contain everything to run, including code. But this approach opens a lot of questions.
Well, you can always share an archive with your code and assets You can also use webpack to create a bundled, product-ready version: We have a great sample for that here: RaananW/babylonjs-webpack-es6: Babylon.js basic scene with typescript, webpack, es6 modules, editorconfig, eslint, hot loading and more. Will even make coffee if you ask nicely. (github.com)
I’m not sure what extra value a serializer would provide, but I could definitely be missing something.
The idea behind this was a self running package, one file, OS targeted executable, which could start a local webserver, spawn a browser instance in kiosk mode, unpack the app and run it as a full screen app. I am not advocating this idea though, it just popped out of my mind.