In our case, users have created about 1,500 template documents in 7 languages. I’d be lynched if I didn’t provide a path to convert them.
Paul > On 29 Aug 2018, at 21:56, Richard Wright via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > That’s what I was afraid of. Does it not occur to anyone at 4D that people > have existing code to manipulate 4D Write documents and that that code has to > be rewritten to work with 4D Write Pro? The lack of a command cross reference > makes the process unnecessarily difficult and maybe you end up 90% through > the process only to find out that a certain functionality has not been > retained in “Pro". How hard could it be to write such a thing? After all, > when 4D Write Pro was being written, surely the starting point would have > been to retain all existing features and then give us all the great new > things. So you create a list of existing commands and then you check them off > as those functions are rewritten in “Pro”. How else could you know that you > haven’t missed something? Reading a bunch of blogs is not all the same thing > as an accurate cross reference. > > ------------------------------------------------ > Richard Wright > DataDomain > rwri...@datadomainsoftware.com > ———————————————————————— > > >> Date: Wed, 29 Aug 2018 18:57:19 +0000 >> From: Vance Villanueva <vvillanu...@4d.com> >> >> Hi Richard, >> >> 4D Write Pro is a newly developed architecture. There are no cross >> references of 4D Write Pro commands from 4D Write. We have resources to >> convert 4D Write docs to 4D Write Pro. Also, we have resources of 4D Write >> Pro in doc.4d.com, blog.4d.com, and kb.4d.com for the transition from 4D >> Write. >> >> Regards, >> >> Vance Villanueva >> >> >> >> >> -----Original Message----- >> From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Richard >> Wright via 4D_Tech >> Sent: Wednesday, August 29, 2018 9:45 AM >> To: 4d_tech@lists.4d.com >> Cc: Richard Wright >> Subject: 4D Write to 4D Write Pro >> >> Is there a cross reference of language commands between 4D Write and 4D >> Write Pro or do we have to all figure it out for ourselves? >> >> I’m mystified as to why wrappers for the old commands could not have been >> created so as to make the move to 4D Write Pro relatively painless. E-node >> did this very nicely when they created the new API for AreaList. All the old >> commands still work because they are internally mapped to the new ones. Why >> can’t this be done for 4D Write Pro? If it’s truly ready to go, scrap 4D >> Write but create a shell plugin that maps all the old commands to the new. >> With Mac Mojave being the last OS to support 32 applications it’s going to >> get serious pretty soon. >> >> ------------------------------------------------ >> Richard Wright >> DataDomain >> rwri...@datadomainsoftware.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 **********************************************************************
