My apologize in advance to ask such a dumb question and then… this late in the process.
May be yours know I’ve been using (and pushing for) the GUI Editor since its early alpha.
However, it’s only now that I ask myself “How do I move this thingy to production”. I mean, efficiently.
So, I had started sketching my GUI in the Editor. Didn’t stop there. Ended-up building the entire GUI and while loading from the snippet, needed to host all my image links in a ‘reliable source’ storage (my dropbox). So now, all links in the editor come from my dropbox, right!
Question is: If I now want to move to production and host the GUI on my server (obviously loading it from the JSON), how am I supposed to proceed to have my images replaced by the ones on my server? I mean I know of the tedious way, but … anyone ever had a thought about this? what am I missing?
Thanks in advance for your help and meanwhile, have a great day
I use vue+vite.
I start inspector from the project and open the gui editor, so that it can access the images in the project folder using absolute paths.
For example /img/something.jpg can be accessed as /public/img/something.jpg.
After modifying the gui, I just save it as a json and reload it.
Thanks, but that’s exactly what I ment when I said “the tedious way”. Admit we would want to turn this editor thingy into a tool that can really be used in production (and return to it to make further changes) WITHOUT THE NEED of external apps/framework (like vue or vite or whatever)… unless, as I said, there’s something I missed (which is indeed possible), I was rather thinking of a solution that would let us, IE:
Enter a path for production for all assets
On each link, have 2 links. The default/snippet driven - pre-prod. Name it the way you want AND… another link that would take the production path and would just need to enter the image name (or subfolder and name if applicable)
And then, on save, have the options to save using pre-prod or production links.
Would that make any sort of sense to anyone out there? cc @carolhmj
No worries. English is also not my language. I’m not using a translator but parts of my content can certainly be ‘challenged’ or remain ‘obscure’
With that said, yes, it can help for my ‘current situation’ since I already created everything, I will indeed need an in-between step process to restore it to what I need. So much for me There’s no way to go back in time But I was more thinking about the future (and make sure I didn’t miss anything on what we currently have).
Again, I very much value your input. Might come in handy. We’ll see.
Meanwhile, have an awesome day
what we could think of is a new parameter for the GUI loader that will automatically remove the current root of the images link and replaced it with your own root
Thanks a lot for taking the time to look at my errants I’m sure you have more urgent matters to take care of with the imminent release of v7. You must be starting to feel the pressure , are you ? And, Yes, this would sound like something we could use. May be you want to wait a little and double check this with your Team before moving on. As I said, I can deal with the current situation (in a way I create it )… just wanted to make sure we continue to look at the best way to improve this for the future (and have more people commit to BJS GUI ).
Thanks again and meanwhile, have a great day
Yes, of course, this way or another it’s basically what will happen here. But as I said, “tedious”, OK, a little ‘tedious’… Anybody here noticed I’m the ‘lazy guy’?
Jokes apart, I’m thinking if I have to go through this entire process each time I want to ‘test and improve’ my GUI and push new to production… I’m gonna have to go through this every time
But I was more thinking about the future (and make sure I didn’t miss anything on what we currently have).
)… just wanted to make sure we continue to look at the best way to improve this for the future (and have more people commit to BJS GUI 
).
I will add that parameter for you in the GUI deserializer