On 01/16/2012 02:09 PM, Caolán McNamara wrote:
On Mon, 2012-01-16 at 09:18 +0100, Stephan Bergmann wrote:
The UNO concept is to thread the (one and only) component context
instance through the code
Does the configmgr need the component context just for
Components::getExternalValue, which I ima
On Mon, 2012-01-16 at 09:18 +0100, Stephan Bergmann wrote:
> The UNO concept is to thread the (one and only) component context
> instance through the code
Does the configmgr need the component context just for
Components::getExternalValue, which I imagine is to handle stuff like
officecfg/regist
On 01/13/2012 04:14 PM, Michael Meeks wrote:
On Fri, 2012-01-13 at 14:15 +0100, Stephan Bergmann wrote:
UNO *is* the tool to make functionality available to different
languages, to extensions, and to scripting facilities.
Sure - of course. This API, on the other hand, is a C++ syntacti
On Fri, 2012-01-13 at 14:15 +0100, Stephan Bergmann wrote:
> On 01/13/2012 11:23 AM, Michael Meeks wrote:
> > Oooh ! :-) it looks really rather nice; how efficient is the compiled
> > representation ? hopefully much more so than the big chunks of in-lined
> > UNO-ness that existing code uses :
