Perhaps this can be exploited to allow the event model to work better. Better and more messages and callbacks can allow the event model to get things done while people are doing other things.
On the desktop, we might be getting command-line LiveCode back. This means that some tasks can be pushed to a standalone and communication with that is by 'open process' reads and writes, or by TCP/IP. However, I heard somebody mention (dunno who, so this is blatant rumor) that development and stacks being tested will be more isolated, perhaps in separate threads or processes, and there might be some generalization of that that might help. Overall, my feeling is to let the event model work. If we find weaknesses there, then lets ponder those. Dar On Jun 10, 2013, at 2:31 PM, Dr. Hawkins wrote: > On Mon, Jun 10, 2013 at 12:30 PM, Mike Kerner > <mikeker...@roadrunner.com>wrote: > >> Well, now that we are going to get multitasking, I would love to see some >> new tweaks from LC so we can take advantage, like, for example, being able >> to push data updates live, while the device's owner is doing something >> less, umm, productive. >> > > Heck, I'd like even very primitive threading for LC itself, so that I can > update a remote db in the background while the user continues to work, > instead of a potentially multi-second lag. > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
