Lutz writes: >we use a modified version of the mentioned vc-framework component. It saves >all changes in the code to text files >immediately and keeps track of the timestamps of the changes in an external >database. The text files can be >committed to a source code versioning tool like svn, mercurial, git ...
>We extended it a bit to allow reimporting of the exported code. So we are able >to switch between branches and >we can do team development without a development server and dev clients. All >members of our team use single user >instances of 4D. The result of the >development will be compiled into a built/merged server application. >A very old version (V13 yet) with import code can be found on Github: >https://github.com/elutz/vc-framework-v13 Do your apps use 4D forms? If so, how do you deal with them with respect to version control? Thanks, Tom Benedict Optum This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
