|
Title: Subversion - Best practise Post by: Infrastructure T. on June 17, 2011, 09:19:04 am G'Day,
We have a blank canvas in regard to source control and have created a blank svn repository. however now wanting suggestion on best practise for use via studio. Our source is in a fourgen structure I.e. fourjs/accounting/module.4gm/program.4gs/lots of 4gl's and .per's We have external libraries located in fourjs/accounting/I4LIBS/accts/lalookup/one or two .4gl's and .per's Each program has it's own project file with the external dependancies to the libraries. Are the any suggestions / examples of SVN implementation. How are you guys out there Source controlling with Studio? Kind Regards Peter Title: Re: Subversion - Best practise Post by: Olivier E. on June 20, 2011, 01:39:40 pm Hello Peter,
Is your issue the following ? You have an existing application structure on disk build with Fourgen tools, and you would like 1- to import it in Genero Studio. 2- To commit your new Genero application in SVN (= Subversion) Is that correct ? Does this Four Js manual help you ? https://4js.com/online_documentation/fjs-gst-2.32.01-manual-html/svn/User/versioncontrol.html Are there customers who would like to share their experince in converting Fourgen application structure to a Genero Studio one please ? Thank you and regards, Olivier ECKERT - Four Js in Strasbourg (FRANCE) Title: Re: Subversion - Best practise Post by: Infrastructure T. on June 20, 2011, 03:17:54 pm G'Day,
Yes this is in essence the issues we face. We are importing the application(s) into Genero Studio and we have tools to convert our Makefile into Project files. However our real challenge is not how to commit to SVN it's more the best practice for managing or structuring the repository and in turn best practice for the resulting software updates. We are interested in hearing other peoples real life experiences utilising Genero Studio and SVN. Kind regards Peter |