On Fri, Feb 3, 2017 at 7:48 PM, flury olivier <[email protected]> wrote:
> Mostly I to do IP communication between forms started in their own process. > This is where CALL FORM will enhance building solutions a lot. > Until now, it is a mess. > Hi Olivier, thanks for answering! Yes, the old features were lacking in many ways. I tried them, figured out what it took to use them safely...and then used other solutions. (You won't find CALL PROCESS, VARIABLE TO VARIABLE, SET/GET PROCESS VARIABLE anywhere in my code.) But CALL FORM and CALL WORKER look very, very nice indeed. My compliments to whoever designed it. They've one of those rare combinations of economy and power that really are something to be excited about. Can you offer any specific examples of what kind of IP communication tasks you perform (by whatever means)? I really have focused on headless/server-oriented code for a long time. I make 4D UIs for admin and users, but just try to make them look nice and behave sensibly. Not much IP there...tons in the background, but not really in the UI. I'd like to think through some designs and I find that real-world examples are a huge help in that process. So, any real-world examples that people could offer would be a big help. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
