You can keep your project in binary mode (even keep it in version 17) and still take advantage of version 18, project mode, and git. Here is what I'm doing.
"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. Now that you have a master branch, you can create a version 18 branch for implementing next version features that take advantage of new 4D 18 capabilities. Just open your source directly in version 18 project mode. You can test the conversion and have both 17 and 18 versions open at the same time as long as you have separate data files. 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. John DeSoi, Ph.D. > On Jan 3, 2020, at 5:17 PM, Tom Benedict via 4D_Tech <[email protected]> > wrote: > > This is a great discussion of best practices and guidelines for 4D Projects > and I hope others chime in. It’s a new world for many of us. I would like to > start using Project Mode, but our apps have hundreds (maybe thousands) of > highlight buttons, which are incompatible. If anyone has built an automated > or even semi-automated way to convert highlight buttons to 3D buttons, I’d > love to hear about it. ********************************************************************** 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] **********************************************************************
