Hi Florian,
On Wed, 2014-10-01 at 16:55 +0200, Florian Haftmann wrote:
The current matter of affairs is now documented in the Wiki.
https://wiki.documentfoundation.org/Development/LHM_LiMux#Priority_Main_Loop
To be continued…
Yep - a very helpful table there. I've asked to have that sorted by
timeout not source-location; and to have all the UI related timeouts
split to their own section - clearly we don't want to screw with those -
humans don't get faster reactions with better CPUs ;-)
Then we should rank and prioritise all the small value timeouts into a
series of grouped 'idle' priorities [ some integer ranking I guess cf.
glib idle handlers ] which we can use in place of any timeout to ensure
these are executed as quickly as possible (absent any other timeout) but
in a way that makes reasonable sense =)
Does that make sense ?
Thanks !
Michael.
--
michael.meeks@collabora.com <><, Pseudo Engineer, itinerant idiot
Context
- Re: LiMux student "kick-off" (continued)
Re: LiMux student "kick-off" · Wols Lists
Re: LiMux student "kick-off" · Matúš Kukan
Re: LiMux student "kick-off" · Florian Haftmann
Re: LiMux student "kick-off" · Florian Haftmann
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.