John DeSoi, Ph.D. Thanks for offering your workflow, John. This is very interesting.
> "Master" branch is version 17. When I want to commit a new version I have a > 4D method that copies the structure, opens it in 4D 18, and then exports the > structure in project mode format. This can be completely automated and only > takes a few seconds. How large is your structure? I ask, because our structure has around a million lines of code and probably 15,000 forms and when I’ve tried exporting under 17r5 it takes many minutes. Also, my attempt at setting up a git repository ran into similar performance issues, only hours instead of minutes. I lost interest at that point. > You can continue to make version 17 changes, export, and then merge into your > 18 branch. At some point in the future, all your conversion issues will be > resolved and you can promote the 18 branch as master and deploy with 4D 18. This sounds almost like magic. When you “merge” how do you know what code takes priority? Do you have to examine each method and form? BTW, did you have prior experience with git? I’m asking because my past attempts to get a conceptual understanding of git and version control have had limited success. I found the concepts and terminology overwhelming and couldn't map the git workflow to my 4D workflow at all. I’m looking forward to more posts like yours which provides ‘just enough’ git to get started. Tom Benedict ********************************************************************** 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] **********************************************************************
