> > On Dec 7, 2018, at 1:07 PM, Kirk Brooks via 4D_Tech <[email protected]> > wrote: > > I'm not familiar with VC_Framework but the big improvement in R3 is the > addition of Form convert to dynamic. This allows you to export all the > forms - not just the object and form methods. The objects created are > fully functional dynamic form objects. This is the last piece we needed to > be able to fully build a database from exported files.
17 R3 is not quite there for exporting forms in a way that can easily be moved to another structure. Form convert to dynamic does not include the form or object method paths. I'm hoping that will change, see the recent discussion on the forum. If you export the forms from the structure (not using Form convert to dynamic), the form/object method references are there. But I don't think you can use that to reload the form in another database because the method property can only be a project method. So to use the form in another database you would have to translate the form/object methods into a project methods somehow. > It's easy to diff > folders with methods or form definitions. I've done this with folders > containing thousands of methods in a couple of minutes. The other way to do it is to just export all the files to the same version controlled directory. The commit for each release. The version control tool will show exactly which files are changed since the last release and tracks all changes over time. For 4D, you'll just need to add something to remove methods that have been deleted or renamed. Git automatically figures out when a file has been renamed instead of deleted. John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
