Doug, Just for discussion sake, I'd say that a good portion of long established systems have 100% of their space already occupied by classic code....
The use of the Form object offers so much that I am resigned to let go of some generic code, not happy, but willing to pay that price. Lahav -----Original Message----- From: 4D_Tech <[email protected]> On Behalf Of Douglas von Roeder via 4D_Tech Sent: Thursday, April 30, 2020 5:51 PM To: 4D iNug Technical <[email protected]> Cc: Douglas von Roeder <[email protected]> Subject: Re: Object notation replacement for use of Self in a script — v18 Randy: "If there is such an issue trying to get object values to work right, what’s the reason to use them at all?” The new language is extremely powerful and I found it quite easy to pick up (mostly). The fact that it doesn’t give us 100% backward compatibility is not unexpected. "I know everyone is all excited about object notation, but it’s not mandatory. Why should we even consider using it if doesn’t do what we need? I’m sure there are some areas where it’s useful, but it sounds like there’s a lot where it isn’t. Am I missing something” “[doing everything that] we need” is a pretty high bar, wouldn’t you agree? For me, I’ve been using ObjectTools + constructors since the late 90’s, biding my time for 4D to adopt objects/object notation/OOP. At this point, I’ll take what I can get. While I was quite not-happy with this particular limitation (I have forms with hundreds of fields that use Object name that are used with Object get pointer), I think the last paragraph of Miyako’s posting, above, is sound advice - "I would focus my use of object notation to areas where classic code could not go, not spaces already occupied by classic code." -- Douglas von Roeder 949-910-4084 On Thu, Apr 30, 2020 at 3:03 PM Randy Kaempen via 4D_Tech < [email protected]> wrote: > > > On Apr 30, 2020, at 4:43 PM, lists via 4D_Tech > > <[email protected]> > wrote: > > > > OK, based on this design, we are back to using variables (or dynamic > variables) for data entry of anything that needs any kind of > processing done to it after an entry, having to load the values to > these data entry objects when loading the form, and copying the values > back when we want to save any user changes. > > > > OR > > > > We can use the Form.XXX notation to gain the advantage of that new > > nifty > option, but lose the generic coding ability. > > > > I'd say it's a choice, but the lack of the ability to address an > > object > from within generically definitely seems to be a glaring omission... > > If there is such an issue trying to get object values to work right, > what’s the reason to use them at all? > > I know everyone is all excited about object notation, but it’s not > mandatory. Why should we even consider using it if doesn’t do what we > need? I’m sure there are some areas where it’s useful, but it sounds > like there’s a lot where it isn’t. Am I missing something? > > > Randy Kaempen > Intellex Corporation > > ********************************************************************** > 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] > ********************************************************************** ********************************************************************** 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] ********************************************************************** ********************************************************************** 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] **********************************************************************
