Hi Lubos,
On 2011-04-04 at 14:13 +0200, Lubos Lunak wrote:
I just finished the audit of component_writeInfo usage - which (it
seems) is the sign of bit-rotted code (for built-in components at
least).
Lubos - I couldn't quickly work out what is going on with:
fpicker/source/unx/kde_unx/UnxFPentry.cxx
which has a component_writeInfo - but is one of three directories all
doing kde file picker stuff; thoughts appreciated.
fpicker/source/unx/kde - standalone helper actually using KDE3 libraries and
implementing the KDE3 file picker
fpicker/source/unx/kde_unx - LO code which interacts with the standalone
helper (KDE3 integration only)
fpicker/source/unx/kde4 - KDE4 integration, independent of the two above
But I can't comment on component_writeInfo itself, as I have no clue what
that is and the code looks as something LO-related rather than KDE-related.
Maybe Kendy knows.
So - what we need is to get rid of the component_writeInfo in the KDE3
code, and instead create the new xml .component file - similar to the
Gnome one, I'd say.
Regards,
Kendy
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.