Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index



On Thu, 2012-12-13 at 08:51 +0200, Noel Grandin wrote:
IIRC, Cairo also runs on win32, so why not using it instead of gdi+ ?

        We actually shipped a version using the cairo canvas by mistake at some
stage - that caused serious grief because of a (IIRC now fixed) font
rendering nasty.

How is cairo's performance against gdi+ on Windows?  Do you know?

        Any discussion of performance without profiling is just a total waste
of time :-) I would put very good money on the poor draw / drawinglayer
performance around rendering large documents being -absolutely-nothing-
to do with either cairo or VCL, and everything to do with dumb
algorithmic stupidities caused by layering, and hidden behind some
otherwise apparently obvious code :-) We can push pixels at blinding
speed - but if the real problem is an N^3 in the rendering path in the
number of objects it's not going to help at-all ;-)

        So - where's the profile ? more to the point - where is the
document ? :-) Kohei - I assume this is your nice class diagram /
documentation ? if so - I'd love to have the canonical version of that
in git / core as a flat odg (flat so revision control is meaningful and
reasonable small). Far too few people know about your good work there
IMHO.

        ATB,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.