Hi Garri, Thank’s for responding.
I’m reasonably solid with variable/field naming, I think (at least once I get updated to include blobs and object types). As far as forms and method names go though, my approach developed organically over the years and really only applied to a single app so isn’t ideal. I’m looking for some suggestions that can be applied more generally. Sounds like that’s what you’ve done. I would like to see what you’ve done. Thanks, Tom > On Dec 18, 2018, at 14:08, Garri Ogata via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Tom, > > I use a naming convention and a set of methods that gets created for every > module and form. I have used it with multiple programmers some where working > on a server and some remotely. I would be glad to share with you if you like. > Most of it is documented. It is based on using a four letter acronym for each > module. > > Feel free to contact me via email if you are interested. > > Garri > ________________________________ > From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of Jody Bevan via > 4D_Tech <4d_tech@lists.4d.com> > Sent: Tuesday, December 18, 2018 7:43 PM > To: 4D iNug Technical > Cc: Jody Bevan > Subject: Re: Coding/Development Style Guide? > > Tom: > > We rewrote our shell for v16 from scratch. I also wanted to write complete > documentation on using the shell too. That of course included naming > convention for everything (even table names), includes lots of code that is > very easy to add to code you are writing, and explanation of a lot of the > code, and how to do things. The manual is just under 300 pages currently. > > The naming convention (and the shell) is the result of many years of > development with multiple developers and thousands of end users. It has been > put through the wringer a few times over. > > Sadly, I have not felt the need to complete the manual (I figure it is about > 50% done). > > Jody > > Argus Productions Inc. > > > >> On Dec 14, 2018, at 9:28 AM, Tom Benedict via 4D_Tech <4d_tech@lists.4d.com> >> wrote: >> >> Anybody out there have a style guide for development that they’ve written? I >> know a lot of people use shells that either they or others have written and >> that goes a long way toward supporting ease of maintenance of an app. Have >> you formalized guidelines on coding style, UI standards, naming conventions >> etc? I’m especially looking for examples that have worked well in team >> development. >> >> Thanks for any input. >> >> 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:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
