Babylon Js Editor: Saving, Reloading and Workflow Lifecycle

@julien-moreau

I have gotten this workflow to happen! Thanks to your support and your answers I have a repo going. There are some quirks, but I can go over those later. The GitHub repository is here:

If you see this message early, you will not yet see anything in the ReadMe.md. I plan to write that up in the morning. I plan to take my time and make this very clear and use images, so that it can be used (after you review) for the babylon documentation.

In the process of working on this, I have noticed a couple of smaller issues. One of them is worth mentioning here:

There is some potential for mistakes as you’re saving to the two different locations because the file system remembers the last location.

If you …

  1. select ‘Save project as’, and you select the project folder in ‘editor-projects’, you’re doing what you need to.
  2. Then let us say you work for a while, and then you Export Final Scene and Assets. Ok now you select the scenes folder in the webapp, which is also intentional.
  3. The problem is that doing CTRL+S is now pointing at the webapp. You need to do the ‘save as’ option each time and navigate to and fro. Because the person using the editor likely has the same folder name in both places, it could be easy to stomp over the wrong thing, such as saving the editor-project into the web-app’s scenes/ folder with CTRL+S after doing an Export Final Scene and Assets operation.

This is a minor annoyance, but something I had to be very aware of while working, because I did overwrite over the wrong folder once.

The other I’ve made another forum issue:

Another minor question: how do I get rid of those editor-only labels you have in the init project? What are those?
image