I don’t use the traditional output form/input form drill down either. But your 
question is exactly the one I’m trying to explore. I think most of us have 
traditionally programmed in 4D with one process for each window. Up until now 
all these “processes” were really on the same thread as far as the OS was 
concerned and 4D was doing the time slicing. With the introduction of 
preemptive processes, we now have the ability to have our code run on different 
OS threads. All the other environments I know of use one thread for all the UI 
and other threads as needed for background or potentially long running tasks. 
This is akin to putting all our windows in the Application process and using 
preemptive processes for background tasks. If I heard right, Thomas alluded to 
this as an idea if you had the chance to start an app from scratch.

I suppose if we continue to use normal processes for windows and 4D continues 
to time-slice on the UI thread, it amounts to the same thing. So, is there a 
benefit to keeping all UI in the Application process? Does it out-weigh the 
costs of doing it? I’m really not sure, but that is what I’m trying to think 
through and understand.

--
Cannon Smith
Synergy Farm Solutions Inc.
Hill Spring, AB Canada
403-626-3236
<[email protected]>
<www.synergyfarmsolutions.com>


> On Sep 14, 2016, at 2:26 AM, Kirk Brooks <[email protected]> wrote:
> 
> What's the benefit of doing that? In my typical work I deal with things
> that want to be open in multiple windows, like sales orders, items, trips,
> etc. So I haven't based anything on the 'traditional' output form/input
> form / drill-down architecture for - a really long time. Is that the kind
> of situation this would be a benefit for?
> 

**********************************************************************
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