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


On 03/01/2012 10:25 PM, Michael Meeks wrote:
On Thu, 2012-03-01 at 20:47 +0100, Stephan Bergmann wrote:
AA:             + l/strace-alike for UNO (Stephan)

On a more constructive note  ;)  the above already exists, in the form
of<http://wiki.services.openoffice.org/wiki/Uno/Spec/Log_Environment>.

        Great - so then, perhaps the GSOC task might be polishing this - making
it easy to use [ in particular tracing ~everything a-la strace by
default and using using grep later is a rather useful thing ].

        Also - we need a dynamic_cast<>  alike that hides the UNO tunnel-ness,
and (hopefully) does it more simply / easily too - otherwise (I guess)
all of that breaks when we start to trace - though some easy way to
implement XTunnel (or preferably the absence of a need to - surely UNO
knows / can do that for us ? ) would be wonderful.

Micheal, I think I still don't understand what you are up to here. What does logging have to do with XUnoTunnel? (And we want as little as possible of the XUnoTunnel hack, anyway, so no idea what your "dynamic_cast<> alike" idea is?)

        Do you think there is enough there to do for a GSOC project ? I guess
we could add a few of the LibreOffice4 UNO migration things into there
otherwise; perhaps the types.rdb replacement idea ?

Make it into a "random UNO improvements" project?  Hm, not sure.

Stephan

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.