On Sep 3, 2019, at 7:09 PM, Tom Benedict wrote: > The “trick” to converting Write Classic to Write Pro is to abandon any idea > that it will be easy or quick. It will likely take way longer than you > estimate. You also need to give up any concept of how things are done in > Write Classic. Write Pro uses a completely different approach. It is an > “additive” environment, where the default is basic and you have to add > features and functionality. That’s the opposite of Write Classic, which > started with all the features turned on and you had to turn them off as > needed.
+1 What Tom said. I too have just done a conversion of 4D Write Plugin to 4D Write Pro that had a lot of 4D Write Plugin code that did many things. You have to throw it all away and start over. There is no one-to-one, command-for-command conversion for 4D Write Plugin code to 4D Write Pro code. You have to learn all new concepts of how 4D Write Pro works. Once you’ve got that, you can then determine what code you need to write to do what you want. It’s not going to be a 1 hour or 1 day job to do the conversion if you have many hundreds of lines of code that used 4D Write Plugin. Plan on spending a week or more. It’s one of those “grin and bear it” type situations. On Sep 3, 2019, at 7:09 PM, Charles Miller wrote: > Any ideas how we might proceed? Does anyone know 4D's plans re > implementing all 4D write features in 4D write pro and if so when that > might occur. There are some features you may need that are not in v17.x, but are in v17 R versions. (Horizontal toolbar is one you you may want/need. I did.) So if you need one of those features you will have to wait for v18.0 or go with v17 R5 or v17 R6. One thing to keep in mind is that v18 will have zero 4D Write Plug support since v18 will be pure 64bit and the 4D Write Plugin is 32bit. I wanted to be able to compare converted documents to make sure the 4D Write Pro version printed and looked the same as the 4D Plugin version. It’s easy to do that if you run v17 32bit version. You can write 4D Write Plugin code and run it and also write 4D Write Pro code and run it side by side. What I did was create a new object field in my [LetterTemplates] table to store a 4D Write Pro version of the 4D Write Plugin blob field. Then I could tweak the 4D Write Plugin version to get it to build a document that converts perfectly with 4D Write Pro. For me it was about 95% perfect in the conversion, but not 100%. I had to do a few tweaks here and there to get it right. Here is the code in the trigger for the table: // convert 4D Write area to 4D Write Pro [LetterTemplates]LetterPro:=WP New([LetterTemplates]Letter_) WP SET ATTRIBUTES([LetterTemplates]LetterPro;wk layout unit;wk unit inch) That’s it. All editing and changes were still make in the 4D Write Plugin area. The 4D Write Pro field is just there to support users printing and using the Letter Templates. And I could have 2 code paths in the application. The old 4D Write Plugin code path that only works in the 32bit version, or the 4D Write Pro code path that works in both 32bit and 64bit version. That let me roll out the 4D Write Pro version selectively to users. If something got “broke” in 4D Write Pro, I could just set a preference for that user to use the old 4D Write Plugin code and have it work like it did before. Once v18 is released and I’m ready to upgrade my client, I’ll convert to v18 and then do a compile and go clean up all the 4D Write Plugin errors that will occur since the plugin will not exist in the v18 version. And I’ll just delete the 4D Write Plugin blob field. It will no longer be needed. That’s how I’m handling it. One last thing. 4D Write Pro does not support all the fonts that 4D Write Plugin does. Some “old format” fonts — there was a “script” font people were using for signatures — can’t be used with 4D Write Pro. I had to write some 4D Write Plugin code to search out all instances of this old font and switch it to another font. A few hours work. Not a big deal. But these are the things you can run into when you do a 4D Write Plugin to 4D Write Pro conversion. Tim ***************************************** Tim Nevels Innovative Solutions 785-749-3444 [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] **********************************************************************
