But what if the structure was that collection of files and that 4D runs as it always does but the github version management is always in play without an export? What if the .4db is simply a package that didn’t have to be there? Just a thought. I think at a minimum, we will be one mouse-click from exporting the code, as you can see from the new v17r3 release and I’m assuming we’ll be able to import that same code to build a .4b from scratch. My idea saves the conversion steps, all other functionality would be identical.
FWIW, Robert Sent from my iPhone > On Oct 23, 2018, at 3:36 AM, Epperlein, Lutz (agendo) via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > No, I don't think so. It would be a complete different system. 4D relies on > the structure file, it is a database of code and other information, UI and so > on. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
