Some people use the word "Preview” to describe software that not be used in production. some use Beta , 4D uses R# to describe non production software
I personally use beta and will have multiple beta releases. The R# nomenclature is a fine strategy, its then easy to see the non-production development progression > On Mar 13, 2019, at 2:00 PM, <4d_tech-requ...@lists.4d.com> > <4d_tech-requ...@lists.4d.com> wrote: > > Send 4D_Tech mailing list submissions to > 4d_tech@lists.4d.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.4d.com/mailman/listinfo/4d_tech > or, via email, send a message with subject or body 'help' to > 4d_tech-requ...@lists.4d.com > > You can reach the person managing the list at > 4d_tech-ow...@lists.4d.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of 4D_Tech digest..." > > > Today's Topics: > > 1. Re: 4D V16 R6 Vs 4D V16.5 (Bernd Fröhlich) > 2. Re: 4D V16 R6 Vs 4D V16.5 (Milan Adamov) > 3. Re: 4D V16 R6 Vs 4D V16.5 (Jeffrey Kain) > 4. Re: 4D V16 R6 Vs 4D V16.5 (GI -AJAR) > 5. Re: 4D V16 R6 Vs 4D V16.5 (Jeffrey Kain) > 6. Re: Printing forms modified with Duplicate Object (Alan Tilson) > 7. Re: Moving a served v15.4 Windows DB to Mac v15.4 standalone > (Perkins, Bradley D) > 8. Re: Printing forms modified with Duplicate Object (Alan Tilson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 Mar 2019 11:14:47 +0100 > From: Bernd Fröhlich <b...@eaglesoft.de> > To: 4d_tech@lists.4d.com > Subject: Re: 4D V16 R6 Vs 4D V16.5 > Message-ID: <201903131114470...@bremac.de> > Content-Type: text/plain; charset=ISO-8859-1 > > Milan Adamov: > >> But there not announced as v16 features, that is simply not true, no one >> ever said that. On the contrary, it is explicitly said and written many >> times that those features are upcoming features in next major version. > > So it IS a V17 beta after all... > > Maybe all the folks at 4D understand how those R version numbering works, but > for the rest of the world it is obviously quite confusing. > > Gruß aus Bremen, > Bernd Fröhlich > > > ------------------------------ > > Message: 2 > Date: Wed, 13 Mar 2019 12:21:21 +0100 > From: Milan Adamov <mada...@mac.com> > To: 4D iNug Technical <4d_tech@lists.4d.com> > Subject: Re: 4D V16 R6 Vs 4D V16.5 > Message-ID: <19d70d6b-58f6-41a9-a1b8-fdb031843...@mac.com> > Content-Type: text/plain; charset=utf-8 > > > >> On Mar 13, 2019, at 11:14 AM, Bernd Fröhlich via 4D_Tech >> <4d_tech@lists.4d.com> wrote: >> >> Milan Adamov: >> >>> But there not announced as v16 features, that is simply not true, no one >>> ever said that. On the contrary, it is explicitly said and written many >>> times that those features are upcoming features in next major version. >> >> So it IS a V17 beta after all... >> >> Maybe all the folks at 4D understand how those R version numbering works, >> but for the rest of the world it is obviously quite confusing. >> >> > > No it isn’t. If it is beta that would mean you would have all of planned > features for v17 implemented and still in testing within 4D, in R version > there is beta phase of R version which is done and the subset of new fetures > is fully tested by QA and Partners before release. For example, current R > version is v17 R3, v17 R4 is in beta. Calling it v17 beta 3 would not solve > the problem for those that are confused, on the contrary, it would add more > confusion to it. > > It seems that you don’t have a problem with nomenclature, but the all R > version approach of doing things incrementally. > > > Milan > > P.S. I am not with for 4D for more than a year now. > > > > ------------------------------ > > Message: 3 > Date: Wed, 13 Mar 2019 08:16:01 -0400 > From: Jeffrey Kain <jeffrey.k...@gmail.com> > To: 4D iNug Technical <4d_tech@lists.4d.com> > Subject: Re: 4D V16 R6 Vs 4D V16.5 > Message-ID: <ea57ad1f-e650-408f-99ce-8f266ad6d...@gmail.com> > Content-Type: text/plain; charset=utf-8 > > It's really not that hard, nor that unusual. > > Is Windows Server 2008R2 a beta of Windows Server 2012? Nope. It's an > incremental release with new features. > >> On Mar 13, 2019, at 6:14 AM, Bernd Fröhlich via 4D_Tech >> <4d_tech@lists.4d.com> wrote: >> >> Maybe all the folks at 4D understand how those R version numbering works, >> but for the rest of the world it is obviously quite confusing. > > > > ------------------------------ > > Message: 4 > Date: Wed, 13 Mar 2019 14:02:27 +0100 > From: GI -AJAR <gabriel.inziri...@ajar.ch> > To: 4D iNug Technical <4d_tech@lists.4d.com> > Subject: Re: 4D V16 R6 Vs 4D V16.5 > Message-ID: <17e9fb22-0e95-4915-be79-be395ae08...@ajar.ch> > Content-Type: text/plain; charset=utf-8 > > Hi, > > For me too it is not confusing. Actually to call it V17 beta is not only more > confusing but it is wrong. > > Actually you can see v17 as a 16 R7 if you like. > > R release make it easier to go through the new features 4D implement by > having them little by little instead to have a full load of new features > after 1 and half year. I really think this way of doing is more performant > and more nice for developers to test things and to give feedback. > > I think it improve the quality of 4D. > > Envoyé de mon iPhone > >> Le 13 mars 2019 à 13:16, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> a >> écrit : >> >> It's really not that hard, nor that unusual. >> >> Is Windows Server 2008R2 a beta of Windows Server 2012? Nope. It's an >> incremental release with new features. >> >>> On Mar 13, 2019, at 6:14 AM, Bernd Fröhlich via 4D_Tech >>> <4d_tech@lists.4d.com> wrote: >>> >>> Maybe all the folks at 4D understand how those R version numbering works, >>> but for the rest of the world it is obviously quite confusing. >> >> ********************************************************************** >> 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 >> ********************************************************************** > > > > > ------------------------------ > > Message: 5 > Date: Wed, 13 Mar 2019 09:43:11 -0400 > From: Jeffrey Kain <jeffrey.k...@gmail.com> > To: 4D iNug Technical <4d_tech@lists.4d.com> > Subject: Re: 4D V16 R6 Vs 4D V16.5 > Message-ID: <5180e3ac-1397-4530-81f7-d913ad24c...@gmail.com> > Content-Type: text/plain; charset=us-ascii > > I definitely agree that 4D's new internal processes and continuous delivery > model have improved product quality a LOT. There's no way I would have ever > considered putting a .0 release into production, but we did just that with > v17.0. > >> On Mar 13, 2019, at 9:02 AM, GI -AJAR via 4D_Tech <4d_tech@lists.4d.com> >> wrote: >> >> I think it improve the quality of 4D. > > > > ------------------------------ > > Message: 6 > Date: Wed, 13 Mar 2019 13:16:47 -0400 > From: Alan Tilson <alantil...@gmail.com> > To: 4D iNug Technical <4d_tech@lists.4d.com> > Subject: Re: Printing forms modified with Duplicate Object > Message-ID: > <CAGwcqE-M2Ve5corjNFfOj=7ojz219+cufbzzfauwwo_hfzn...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hello Miyako, > Ok, I'm back to this project. > Thanks for the info and I'm working with the Print Object command, trying > to anyway. > But it doesn't print subforms... > And you said I need 17R to convert an existing form to JSON...we're running > 17.0. > Any additional advice would be appreciated. > I'll try check out your component db to see how you did the labels. > Thanks, > Alan > > On Wed, Mar 6, 2019 at 7:41 PM Keisuke Miyako via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > >> have you looked into the "Print object" command? >> >> you don't need to duplicate an object, >> you can print the same object as many times as you like, >> at any position (decimal, not integer positioning) >> >> with 17R you can define an object (JSON) representation of a form from >> scratch, >> or take an existing form, convert to JSON and add or subtract objects. >> >>> 2019/03/07 7:40、Alan Tilson <alantil...@gmail.com>のメール: >>> Any ideas would be appreciated! >> >> >> >> >> ********************************************************************** >> 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 >> ********************************************************************** > > > ------------------------------ > > Message: 7 > Date: Wed, 13 Mar 2019 18:43:34 +0000 > From: "Perkins, Bradley D" <bperk...@lanl.gov> > To: "4d_tech@lists.4d.com" <4d_tech@lists.4d.com> > Subject: Re: Moving a served v15.4 Windows DB to Mac v15.4 standalone > Message-ID: <1913e36a-f7df-4e5e-a5b7-4e9e4c583...@lanl.gov> > Content-Type: text/plain; charset="utf-8" > > Thanks Chuck. I'm not concerned about the Active4D part at this time. It > seemed like in the past there was an issue where you wouldn't be allowed to > open the structure after moving between machines or server -> client. I'll be > at their site tomorrow and will try your suggestion. > > Brad > > On 3/13/19, 3:27 AM, "4d_tech-requ...@lists.4d.com" > <4d_tech-requ...@lists.4d.com> wrote: > > What I would do is take the take the folder the structure is in and > zip it. I would take the folder the data file is in and zip it. I > would then copy both of the zipped archives and proceed./ I am not > sure if there is anything else you need to copy relative to active4D, > buit someone else who uses that can advise > > > ------------------------------ > > Message: 8 > Date: Wed, 13 Mar 2019 14:51:50 -0400 > From: Alan Tilson <alantil...@gmail.com> > To: 4D iNug Technical <4d_tech@lists.4d.com> > Subject: Re: Printing forms modified with Duplicate Object > Message-ID: > <CAGwcqE8dDw7D_tv4tMMg4+-3qjkArUUYf==pgizelto5+z2...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Miyako, > It looks like you just step through all the objects and offset and print > them, so I'm trying that... > Alan > > On Wed, Mar 13, 2019 at 1:16 PM Alan Tilson <alantil...@gmail.com> wrote: > >> Hello Miyako, >> Ok, I'm back to this project. >> Thanks for the info and I'm working with the Print Object command, trying >> to anyway. >> But it doesn't print subforms... >> And you said I need 17R to convert an existing form to JSON...we're >> running 17.0. >> Any additional advice would be appreciated. >> I'll try check out your component db to see how you did the labels. >> Thanks, >> Alan >> >> On Wed, Mar 6, 2019 at 7:41 PM Keisuke Miyako via 4D_Tech < >> 4d_tech@lists.4d.com> wrote: >> >>> have you looked into the "Print object" command? >>> >>> you don't need to duplicate an object, >>> you can print the same object as many times as you like, >>> at any position (decimal, not integer positioning) >>> >>> with 17R you can define an object (JSON) representation of a form from >>> scratch, >>> or take an existing form, convert to JSON and add or subtract objects. >>> >>>> 2019/03/07 7:40、Alan Tilson <alantil...@gmail.com>のメール: >>>> Any ideas would be appreciated! >>> >>> >>> >>> >>> ********************************************************************** >>> 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 >>> ********************************************************************** >> >> > > > ------------------------------ > > Subject: Digest Footer > > ********************************************************************** > 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 > ********************************************************************** > > ------------------------------ > > End of 4D_Tech Digest, Vol 142, Issue 20 > **************************************** ********************************************************************** 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 **********************************************************************
