On 2013-12-04 11:38, Michael Meeks wrote:
Of course, an alternative might be to have a "GUI thread" that does
nothing but run a main-loop, never executing any code - such that we can
always safely yield, and/or create/destroy windows/GCs etc.
Wasn't the idea that
(a) we were going to gradually migrate to running everything on the same thread,
(b) except for the handful of places where parallelism is truly beneficial
(c) and for those parallel places, each parallel chunk would live in it's own little island, interacting as little as
possible with the main thread.
??
Or am I merely projecting my own design ideas onto the past discussions :-)
Disclaimer: http://www.peralex.com/disclaimer.html
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.