We are excited to remind the iNug of the 4DMethod google hangout user group 
meeting next Wednesday featuring a presentation by Thomas Maul:

Special Topic: Messaging with 4D v16

Let’s chat about messaging and how to communicate. No, this isn’t about 
Snapchat, WhatsApp, emoji or digital stickers. This is about building your 
application with a modern multithreaded architecture using commands that reduce 
the problem down to a straightforward approach. Out is the concept of polling 
your variables for a change of status. Messaging uses a push architecture 
delivering state changes to your modularly built application. 4D VP of Product 
Strategy, Thomas Maul, will demonstrate how message passing commands are an 
approachable way for your application code to use the full processing power 
available to it. Learn the details of CALL FORM and CALL WORKER, the new 
commands introduced with 4D v15 R5. These key features will be available to 
everyone with the launch of 4D v16 and will revolutionize how you choose to 
write 4D applications.

Links to join the user group meeting or watch the video later:
https://4dmethod.com/2016/08/01/august-31st-meeting-messaging-with-4d-v16-thomas-maul/

When:
Wednesday, August 31st, 2016 at 12 noon CST

Add event to your calendar:
http://go.4d.com/rs/531-MRT-468/234/Messaging+with+4D+v16%2C+Thomas+Maul.ics<http://go.4d.com/rs/531-MRT-468/234/Messaging+with+4D+v16,+Thomas+Maul.ics>

Add event to your Google Calendar:
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=YWMyYmhkaGFobjAyaWk5bXJxZ3FqMmhudGcgNGRtZXRob2RAbQ&tmsrc=4dmethod%40gmail.com<https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=YWMyYmhkaGFobjAyaWk5bXJxZ3FqMmhudGcgNGRtZXRob2RAbQ&[email protected]>
**********************************************************************
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]
**********************************************************************

Reply via email to